-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Mark tests as expected to fail #2641
Comments
interesting - will need to think about this a bit and how it would co-exist with soft assertions: #1446 maybe we should introduce a |
I think a build-in tag would be nice. My idea would be to evaluate this as the last step after a test is finished. If the tag is present the result is inverted. This way it would not interfere with any other stuff. |
On a first look in the source code I did not find a place where e.g. the other build-in tags are evaluated. If you give me a hint I might prepare a MR. |
@daniel-vergien-bdr the |
@daniel-vergien-bdr @dve merged with thanks, much appreciated ! |
Are 1.5.2-SNAPSHOT versions published somewhere? |
@dve no, I have to push a button to do it. we typically wait for a few more changes to accumulate and release RC versions if teams need something sooner |
I would love a RC as soon as you can do it ;-) And just for the record: the change might be a breaking change if someone used the |
It would be nice to have a way to mark a test a expected to fail. This would come in handy if you write a test for a bug before the bug is fixed.
Junit-pioneer has such a feature: https://junit-pioneer.org/docs/expected-to-fail-tests/
The text was updated successfully, but these errors were encountered: