-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
jqwik should fail property test instead of ignoring it #54
Comments
Well, the test will be marked as ignored together with an ignore message "All parameters must have @forall annotation". Depending on your IDE / build tool configuration this can be as obvious as a test failure. What additional information would a test failure provide? |
For me it would be ok to fail this test with this message. AFAIK gradle reports an skipped test (if reporting) is enabled. But if i want gradle to fail the build i must distinguish between this case and a disabled junit test. For me this is some kind of configuration error.. like @forall for a type without an known Arbitrary. It should fail, because i would not expect, that the test will be skipped. |
Hm. You're right, the behaviour is inconsistent. I'll put it on the TODO list. Should be done in next release. |
Thanks a lot:) |
Fixed in d1f899c |
Available in 1.1.3-SNAPSHOT |
Released in 1.1.3 |
Testing Problem
following kotlin test
should fail, but is ignored (guess: name is not annotated but other is).
Suggested Solution
jqwik should fail such a test.
The text was updated successfully, but these errors were encountered: