Repository navigation
Conversation
Allure Report Summary
Allure TestOps: Allure Ruby GitHub actions run (2026-11-03T11:51:59.742Z) Artifacts used (6)
|
andrcuns
marked this pull request as ready for review
November 3, 2026 16:27
andrcuns
added
pr:breaking change
Collaborator
Author
|
@epszaw One thing I'm noticing here in this PR, why do we show all tests as "new"? Is it because the summary table is always generated from the report, not testops, right? If so, I think we should definitely look in to this, it will be incredibly confusing for anyone using this summary table in combination with testops. Completely unrelated to this change, just mentioning it before I forget 😄 |
This branch has not been deployed
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
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
Cucumber scenarios with the same name in different feature files, or RSpec examples with the same full description in different spec files, can be merged into a single test in Allure. This can hide a real failure as a retry when another test with the same name passes.
This change gives tests stable, file-aware identities so that tests in different files remain separate, even when their displayed names match. These identities do not depend on source line numbers or example order. Cucumber scenario outline rows share the outline's identity, with their parameters distinguishing the individual variants.
Test history compatibility: This change may affect test history in the report. After upgrading, some tests may appear as new, and their history may restart or no longer link to results generated with earlier adapter versions because Allure now identifies them differently.
Checklist