-
Notifications
You must be signed in to change notification settings - Fork 172
DNM: tests: add integrationtest to testing-devel #4010
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: testing-devel
Are you sure you want to change the base?
Conversation
|
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a new integration test scenario for testing-devel. The changes are straightforward, adding a new Kustomization resource and the corresponding IntegrationTestScenario definition. My feedback focuses on clarifying the intended optional status of the test and addressing hardcoded version numbers to improve maintainability and prevent potential issues with outdated test configurations.
| # Remove this label if testing is not optional. | ||
| # test.appstudio.openshift.io/optional: "true" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The label test.appstudio.openshift.io/optional: "true" is currently commented out. If this integration test is intended to be optional, please uncomment this label. If it's meant to be a mandatory test, then the comment on line 7 should be removed to avoid confusion.
test.appstudio.openshift.io/optional: "true"| - name: url | ||
| value: https://gitlab.com/testing-farm/integrations-konflux | ||
| - name: revision | ||
| value: v3.16 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The revision for the resolverRef is hardcoded to v3.16. The introductory comment on line 2 suggests setting the pipeline_tag to the "latest available tag". Hardcoding specific versions can lead to outdated tests if the upstream repository updates. Consider updating this value to the current latest tag or implementing a mechanism to fetch the latest version dynamically. If v3.16 is intentionally fixed for this specific test, please add a comment to clarify this.
value: v3.16 # Fixed version for this test scenario.| value: RHEL-9-Nightly | ||
| - name: ARCH | ||
| value: x86_64 | ||
| - name: IMAGE_TAG |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
/retest |
1 similar comment
|
/retest |
fa906d1 to
95479fa
Compare
95479fa to
5aebd95
Compare
No description provided.