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

testng reports failing jgiven test cases as passing #138

Closed
adrian-herscu opened this issue Oct 6, 2015 · 6 comments
Closed

testng reports failing jgiven test cases as passing #138

adrian-herscu opened this issue Oct 6, 2015 · 6 comments
Assignees
Milestone

Comments

@adrian-herscu
Copy link

Given a TestNG-based test with a data provider
And the data provider provides at least two cases
And one case fails
When running the test
Then the TestNG report should contain one failed case

Instead all tests cases are reported as passing.
This behavior is since version 0.8.3.

@janschaefer
Copy link
Contributor

So the TestNG report is wrong, but the JGiven report is correct?

@adrian-herscu
Copy link
Author

Yes the JGiven report is correct but the TestNG report is wrong.
This has further implications. When running under Maven the build status is always successful. When this happens under a CI server then not failure notifications are sent.

@janschaefer janschaefer added this to the v0.9.1 milestone Oct 6, 2015
@janschaefer janschaefer self-assigned this Oct 6, 2015
@janschaefer
Copy link
Contributor

I actually introduced the bug when I fixed #123. Too bad that my test did not test the TestNg status, but only the JGiven status :-(
The bug is fixed now in the 0.9.1-SNAPSHOT version.

janschaefer pushed a commit that referenced this issue Oct 6, 2015
@janschaefer
Copy link
Contributor

I back ported this fix to 0.8.x and will release a 0.8.4 version with that fix

@janschaefer janschaefer modified the milestones: v0.8.4, v0.9.1 Oct 6, 2015
@janschaefer
Copy link
Contributor

0.8.4 is released with this fix

@janschaefer
Copy link
Contributor

Due to the severity of the issue I also released v0.9.1 with this fix

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

No branches or pull requests

2 participants