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.

Sign up for GitHub

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

Jump to bottom

JUnitShell/GWTTestCase should support -strict/-failOnError flags #10037

Open
Tracked by #10033
niloc132 opened this issue Nov 8, 2024 · 0 comments · May be fixed by #10039
Open
Tracked by #10033

JUnitShell/GWTTestCase should support -strict/-failOnError flags #10037

niloc132 opened this issue Nov 8, 2024 · 0 comments · May be fixed by #10039
Milestone
2.13

Comments

@niloc132
Copy link
Contributor

niloc132 commented Nov 8, 2024 •
edited
Loading

A library may not have 100% test coverage, it would be handy to fail the test if the module has any compilation errors, to fail building more quickly. Likewise, an application could fail its tests rather than pass tests and then fail to build.
@niloc132 niloc132 mentioned this issue Nov 8, 2024
Open
5 tasks
@niloc132 niloc132 changed the title -strict/-failOnError - a library may not have 100% test coverage, it would be handy to fail the test if the module has any compilation errors, to fail building more quickly. JUnitShell/GWTTestCase should support -strict/-failOnError flags Nov 8, 2024
@niloc132 niloc132 added this to the 2.13 milestone Nov 8, 2024
niloc132 added a commit to niloc132/gwt that referenced this issue Nov 8, 2024
@niloc132
Support -strict in test arguments
7f6d6ba 
Fixes gwtproject#10037
This was referenced Nov 8, 2024
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.13
Development

Successfully merging a pull request may close this issue.

Support -strict in test arguments niloc132/gwt
1 participant
@niloc132