Skip to content
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

Provide better console output for failing tests #7

Open
rundis opened this issue Jun 13, 2013 · 2 comments
Open

Provide better console output for failing tests #7

rundis opened this issue Jun 13, 2013 · 2 comments

Comments

@rundis
Copy link
Owner

rundis commented Jun 13, 2013

Currently you get:
Process 'command 'buster'' finished with non-zero exit value 1

Which doesn't convey whether it was a test that failed or something else.

Probably a good idea to have a look at the java plugin test reporter for inspiration.

@johnzeringue
Copy link

Has there been any progress on this issue? I've just started using this plugin and am really liking it, but better output would be a huge upgrade.

I'd also be willing to contribute this myself, although I'd need a push in the right direction having never written Groovy or Gradle plugins.

@rundis
Copy link
Owner Author

rundis commented Jan 21, 2015

I haven't had much time looking at this project lately. For test errors it should be possible to parse the returned junit xml from buster and print out some sort of summary before the exception is thrown.

Check out the following two classes. Shouldn't be to hard improving the error reporting (all errors are still logged in the resulting junit xml, but a nicer summary in the console would be good).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants