Running/debugging test in the browser has escape sequences in the console

[alan-knight]

e.g.

  JsFunction
  notification_test.dart.js:12387 
  00:00 �[32m+1�[0m: constructor exists�[0m
  notification_test.dart.js:12387 
  00:00 �[32m+2�[0m: A group of tests First Test�[0m
  notification_test.dart.js:12387 
  00:00 �[32m+2�[0m: All tests passed!�[0m

[nex3]

Support for running test files directly in the browser is not planned, at least for the near-to-mid future. Browser tests should be run through the test runner.

[alan-knight]

So if I understand the story as it is in the short term.

• There is no support for debugging tests from the runner
• Running tests manually to debug them is discouraged.

The debugging story is run it directly unsupported? Copy and paste it out of the test into somewhere else and debug that? What do we expect to do for things that use unittest but have their own runner. e.g. all current SDK tests.

[nex3]

All debugging stories for browser tests are currently unsupported. That's why #45 is still open. We're still in alpha releases of a pre-1.0.0 version of a complete rewrite of the testing framework—we need to lay a bunch of groundwork before we can start building on it.