#9993 Properly set allure history id#10176
Merged
christian-bromann merged 2 commits intomainfrom Apr 12, 2023
Merged
Conversation
…ount the suite, test name, and all user-given parameters for the calculation of the historyId.
|
@BorisOsipov @christian-bromann I think there is a bug that might be related to this change - testdeck/testdeck#384. Any ideas? |
Member
I've never used testdeck. @HimanshuD-Groove any clues how this bug can be resolved? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Proposed changes
Fixes #9993
The allure historyId should be set correctly by taking into account the suite, test name, and all user-given parameters for the
calculation of the historyId
Types of changes
Checklist
Further comments
Reviewers: @webdriverio/project-committers