Currently, Allure Pytest incorrectly assumes there is zero or one test class in every given nodeid when calculating fullName and subSuite. Since the test above has nodeid module_test.py::TestFoo::TestBar::test_baz, the calculations become invalid.
Given that testCaseId and historyId depend on fullName, these properties are calculated incorrectly as well.
The PR fixes how Allure Pytest handles such cases:
All test classes are now included in fullName (joined with .).
All test classes are now included in the value of the subSuite label (joined with >).
This file contains hidden or 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
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
Pytest supports nested test classes:
Currently, Allure Pytest incorrectly assumes there is zero or one test class in every given nodeid when calculating fullName and subSuite. Since the test above has nodeid module_test.py::TestFoo::TestBar::test_baz, the calculations become invalid.
Given that testCaseId and historyId depend on fullName, these properties are calculated incorrectly as well.
The PR fixes how Allure Pytest handles such cases:
Fixes #868.
Checklist