-
Notifications
You must be signed in to change notification settings - Fork 218
Support pluggable reporters #12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think for the first implementation it would be sufficient if I could specify a reporter via command line. The main use case I consider is using the unittest command without a special reporter locally while developing, but another configuration on the continuous integration server. There I might need the report in the JUnit format (like this) or one of the many other formats. |
I agree; we should definitely also support setting reporters from the command line. |
This is blocked on #48. |
this is needed in order to utilize saucelabs unit testing capabilities, https://docs.saucelabs.com/reference/rest-api/?_ga=1.245459780.1583316598.1430344943#start-js-unit-tests |
I'd love this functionality, along with #48. I had a previous project using unittest which I wrote my own custom configuration to create Dart Koans (See: https://github.com/butlermatt/dart_koans/blob/master/lib/src/config_koans.dart ) I tried to revive this project this evening with Test but it doesn't seem that same configurability is available with test. |
There should be a means for third parties to create reporters that are dynamically loaded and used by unittest.
This is particularly tricky because reporters are likely to be desired on a user-by-user rather than project-by-project basis, so there's some friction to just putting it into a project's pubspec.
The text was updated successfully, but these errors were encountered: