Add logs, stdout and stderr to the allure-pytest-bdd report #763
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
Is there anybody who can take a look at this PR? @veryhappythings @janza @middagj |
|
Hi, @IvanBuruyane ! Thank you for your contribution. That's a useful feature, but it should be covered with tests. Please, add some tests. Here are links that might help you with that: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
Currently allure report for the pytest-bdd framework doesn't include logs, stdout and stderr created during test run. It makes hard to understand what was the root cause of the test failure. In order to fix this I simply added the code from the allure-pytest listener that adds logs, stdout and stderr to the report. Here's a screenshot from the report with logs:
Checklist