Generate consistent history IDs from final test parameters#1323
Open
baev wants to merge 1 commit into
Open
Conversation
github-actions
Bot
added
theme:junit4
baev
added
type:bug
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
1 participant
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
All Allure Java integrations now provide a stable
testCaseId, while the compatibilityhistoryIdis calculated when the test stops. This includes the complete set of non-excluded parameters, including values added through the runtime API, so parameterized executions are grouped and separated consistently.JUnit template iterations use the template identity as their
testCaseIdand retain a hidden per-iteration UniqueId when framework parameter data is unavailable. Custom history calculation is supported throughTestLifecycleListener.beforeTestStop; the legacy adapter-specific protectedgetHistoryIdhooks have been removed.Checklist