🌱 Add test-identifying annotations to e2e resources#2701
Merged
openshift-merge-bot[bot] merged 1 commit intoMay 13, 2026
Merged
Conversation
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
pedjak
force-pushed
the
e2e-test-annotations
branch
from
a73cfdd to
b6e6fa2
Compare
Inject e2e.olm.operatorframework.io/feature and e2e.olm.operatorframework.io/scenario annotations into every resource applied during an e2e scenario. This makes it possible to identify which feature file and scenario produced a given resource when debugging test failures on a cluster. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
pedjak
force-pushed
the
e2e-test-annotations
branch
from
b6e6fa2 to
68cfdfb
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2701 +/- ##
==========================================
- Coverage 68.12% 68.10% -0.02%
==========================================
Files 145 145
Lines 10700 10700
==========================================
- Hits 7289 7287 -2
- Misses 2884 2885 +1
- Partials 527 528 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Contributor
|
/approve |
openshift-ci
Bot
added
the
approved
rashmigottipati
approved these changes
May 13, 2026
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rashmigottipati, tmshort The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-merge-bot
Bot
merged commit 0d6fcd2
into
operator-framework:main
25 checks passed
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.
Description
Inject
e2e.olm.operatorframework.io/featureande2e.olm.operatorframework.io/scenarioannotations into every resource applied during an e2e scenario.Currently, e2e test resources are named with opaque scenario IDs (e.g.,
ce-e3a7f5d2c1b94a2f). When debugging test failures on a cluster, there is no way to tell which feature/scenario a resource belongs to without cross-referencing test logs. These annotations make identification straightforward:The feature name is derived from the feature file path (e.g.,
features/install.feature→install) and the scenario name comes directly from the Godog scenario.Reviewer Checklist