Releases: allure-framework/allure-python
Releases · allure-framework/allure-python
2.16.2
Compare
Sorry, something went wrong.
No results found
🐞 Bug Fixes
fix(pytest-bdd): do not reuse uuid across test runs (via #926 ) - @delatrie
👀 Links
Commits since 2.16.1
2.16.0
Compare
Sorry, something went wrong.
No results found
🚀 New Features
👻 Internal Changes
👀 Links
Commits since 2.15.3
2.15.3
Compare
Sorry, something went wrong.
No results found
2.15.2
Compare
Sorry, something went wrong.
No results found
Set testCaseId for all test results produced by allure_robotframework (via #884 ) - @delatrie
👀 Links
Commits since 2.15.1
2.15.1
Compare
Sorry, something went wrong.
No results found
Set testCaseId for all test results produced by allure_behave (via #883 ) - @delatrie
Add workflow-wide gh actions permissions (via #875 ) - @epszaw
👀 Links
Commits since 2.15.0
2.15.0
Compare
Sorry, something went wrong.
No results found
🚀 New Features
feat: add titlePath to results generated by all allure-python integrations (via #870 ) - @delatrie
🐞 Bug Fixes
fix(pytest): properly include nested classes in fullName, historyId, testCaseId, and subSuite (via #869 ) - @delatrie
👀 Links
Commits since 2.14.3
2.14.3
Compare
Sorry, something went wrong.
No results found
🔬 Improvements
Don't convert built-in (reserved) pytest markers to allure tags (fix #817 ) (via #862 ) - @sharovd
🐞 Bug Fixes
fix(pytest): can't change a fixture's title in pytest 8.4 or later (via #866 ) - @delatrie
👀 Links
Commits since 2.14.2
2.14.2
Compare
Sorry, something went wrong.
No results found
This release fixes a couple of issues with Allure Behave.
🐞 Bug Fixes
extra test results generated after consecutive in-process runs of Behave (#858 , via #860 ) - @delatrie
AttributeError is raised if Allure Behave is set up via AllureHooks (#629 , via #860 ) - @delatrie
👀 Links
Commits since 2.14.1