-
Notifications
You must be signed in to change notification settings - Fork 16
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
If there is Background and 2 or more tests, if 1 test failed the others are also marked as failed. #23
Comments
@vitaliirymar Thanks for reporting this, but unfortunately I cannot reproduce your case. I created a separate test just for this, but it passes normally: Could you please isolate and share your example? |
@HardNorth I managed to reproduce it with |
@vitaliirymar, Please provide any example. Since I also have tests covering Background functionality. |
@HardNorth try this one:
|
@HardNorth one more request - could you please run the same test (no matter with/without Background) with 2 Examples wit the ReportPortalHook() runner:
I see the following - one scenario example is outside the Feature |
Update: The issue is also reproducible with 2 or more regular tests when 1 of them fails, all the other tests are marked as failed, if there is Background. E.g.:
|
* Update CI build workflow * Update build scripts * Add the first integration test * Dependency update * The first Code Reference test, ReportPortal format apply, ignore target folder * Do not output Cucumber to avoid failures in CI * Revert last change * A try to fix tests * Add code reference for simple scenarios * Add code reference for Examples scenarios * Format fixes * Code reference generation: sort by example key to unify code reference * Add Test Case ID * Attribute handling * Fix tests * System attributes reporting add * Refactor item start method * Add more tests * Add scenario parameters reporting * Update property format * Add parameter handling for steps * Add parameter log message verification * Table parameters handling * Background steps handling * Test fixes * Fix typing * Background logic update * Another background test * Fix Table test * Fix Table test * Fix description * Add another test * Add Launch description test * Small fix * Small fix * Add test * Add junit-jupiter-params dependency * Description and item name tests and fixes * Fix test * Refactoring * Add parameter description to examples * Add examples description tests * Refactoring * Add test * Add test * Fix test * Update step logging * Add test * Add another test * Add ReportPortal runtime hook publisher * Refactoring, move common code to util class * Fix parameter reporting * Fix javadocs * ReportPortalHook: WIP * ReportPortalHook: WIP * ReportPortalHook: WIP * ReportPortalHook: Tests WIP * ReportPortalHook: Tests WIP * ReportPortalHook: Tests WIP * ReportPortalHook: Tests WIP * ReportPortalHook: Tests WIP * ReportPortalHook: Tests WIP * ReportPortalHook: Tests WIP * ReportPortalHook: Tests WIP * Add timing test and javadocs * Add feature parameters tests * Bump version * Client version update * Client version update * Fix version number * Update copyrights * Update copyrights * Code format apply * Add README_TEMPLATE.md file * Update README_TEMPLATE.md file * Update release branch * Update release.yml * Update release.yml * Update README.md * Update README.md * Update CHANGELOG.md * Dependency versions update * Actions versions update * Karate version update * Slack link update * Add more tests * Fixes issue #23 - scenarios outside features in parallel execution --------- Co-authored-by: Reingold Shekhtel <13565058+raikbitters@users.noreply.github.com>
Should be fixed in: https://github.com/reportportal/agent-java-karate/releases/tag/5.0.2 |
@HardNorth , the issue is still reproducible. It is related to Background. |
@HardNorth thanks! It's fixed now! |
Describe the bug
In a scenario outline with examples, if 1 example passed and another one failed, the report shows 2 failed tests
Steps to Reproduce
Steps to reproduce the behavior:
Run Scenario Outline with at least 2 Examples where one of them fails.
E.g.
Scenario Outline: Verify math
Given def mathResult = < vara > + < varb >
Then assert mathResult == < result >
Examples:
| vara | varb| result |
| 2 | 2 | 4 |
| 1 | 2 | 5 |
Check ReportPortal results
Expected behavior
ReportPortal displays 1 passed test and 1 failed test
Actual behavior
ReportPortal displays 2 failed tests
The passed test is marked as a failed, but without failed steps and without error log inside the steps.
Dependency versions
agent-java-karate 5.0.0
The text was updated successfully, but these errors were encountered: