fix(pytest): properly include nested classes in fullName, historyId, testCaseId, and subSuite #869
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 calculatingfullName
andsubSuite
. Since the test above has nodeidmodule_test.py::TestFoo::TestBar::test_baz
, the calculations become invalid.Given that
testCaseId
andhistoryId
depend onfullName
, these properties are calculated incorrectly as well.The PR fixes how Allure Pytest handles such cases:
fullName
(joined with.
).subSuite
label (joined with>
).Fixes #868.
Checklist