Support for different output formatter

[Fox32]

The test runner looks very promising in combination with common CI tools. At the moment, only a simple plain text output is given. It also only contains information about passed suites and failed tests. There is no report about all executed tests.

It would be usefull if the output format of the final report could be choosen, so that common CI tools as Jenkins, TeamCity, ... can be supported. Either by including them in the tool or providing a plugin API.

An alternative is to provide a simpel machine readable format (e.g. JSON) that can be processed further to be consumed by other tools.

For some tools it would not just be interesting to receive a final report, but also on the fly progress information.

I know this is a very broad feature request, but I'm not sure what your current plans for this are.

[Fox32]

Ok, there is a verbose option to get all test results. But it would be still useful to have a machine readable format.

[nicolasgarnier]

I was going to mention the verbose option (this give you the passed test suite output). And yes, the JSON output sounds like a good feature request :) I'll add it to the list.

Also we'll be working on enabling Dart tests in common CI offerings specifically. Currently this is close to completion for Travis CI (although browser tests are disabled because they are having issues installing content_shell but we'll work on that) and we are working with drone.io too. (Feel free to suggest more :D)

[Fox32]

Some things that might be useful in JSON output: Test suite name, test name, test group, test duration, test result (pass, exception, failed), test failure description, test log output. Skipped tests would be nice to, but unittest doesn't allow this at the moment.

[travissanderson-wf]

I've got a branch that allows you to specify a custom Dart template for VM tests that can enable this type of thing. We are using it along with some tweaks to dart-junit to get VM tests to drop JUnit-friendly XML files for parsing by CI. So far, I don't have a solution for Browser tests, but maybe just a flag to drop the console/error output in a predictable place to be parsed by a later script into JUnit-friendly XML would work. I would be interested in talking with the maintainers if my branch would be something you'd accept on this repo.