ciscoheat
commented
10 years ago Hi, do I understand correctly that you want a more flexible way of reporting? I think that would be done best by implementing your own Reporter (it has a simple interface, https://github.com/ciscoheat/buddy/blob/master/src/buddy/reporting/Reporter.hx) and do what you want from there. I can add both a command-line and compilation option to specify a custom reporter. What do you think?
For CI right now, Buddy reports the test status on command-line as 0 of ok, and 1 if failed. It uses Travis for its own testing: https://travis-ci.org/ciscoheat/buddy
brendanjerwin
I'm using Buddy primarily on a code base that targets Flash, so accept my twisted perspectives with that in mind. :)
I eventually want to get my Buddy specs running in Continous Integration, and I'm also a big fan of command line test runners.
The flash tests, though, need to run in the Flash Debugger (I use the
opencommand on my Mac).It'd be great if all the tests, no matter the target, reported their results back to a central command line test runner, who was then in charge of displaying the results in a common manner.
I've recently done some testing where my tests work against a node.js server running along side them. It seems to work well enough (once all the cross-origin stuff was worked out..) Perhaps a test runner could start a server and then launch the individual target's test runners. Those 'child' runners would communicate their results back to the server on a well-known port which would then handle the job of actually displaying the results on screen (or writing them to file in the JUnit-style for CI!)