Exploratory testing for Elemental and Rancher Manager interoperability#588
Open
lscalabrini01 wants to merge 2 commits intorancher:mainfrom
Open
Exploratory testing for Elemental and Rancher Manager interoperability#588lscalabrini01 wants to merge 2 commits intorancher:mainfrom
lscalabrini01 wants to merge 2 commits intorancher:mainfrom
Conversation
floatingman
reviewed
Apr 1, 2026
Contributor
floatingman
left a comment
floatingman
left a comment
There was a problem hiding this comment.
Just a few questions, because I don't know.
| 3. **Test tier tags**: `sanity`, `extended`, `stress` | ||
| 4. **PIT (Platform Interoperability Testing) tags**: | ||
| * `pit.daily`: Tests that run daily | ||
| * `pit.elemental`: Daily tests for Harvester setup |
Contributor
There was a problem hiding this comment.
Are the elemental tests also harvester tests?
Contributor
Author
There was a problem hiding this comment.
No, they are not. I’m updating the description
Contributor
Author
There was a problem hiding this comment.
Because elemental_schema.yaml is a test suite, while the Elemental tests are actually a test plan
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
2 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.
This pull request introduces a new Go build tag,
pit.elemental, to enable targeted testing for Elemental setups. The tag is added to documentation and applied across multiple test files to include them in the Elemental test suite. Additionally, the Elemental test suite definition YAML is removed, likely to transition to using the new tag-based approach.Test coverage and build tag updates:
pit.elementalbuild tag in documentation (.github/copilot-instructions.md,TAG_GUIDE.md) to define and describe tests that should run on Elemental setups. [1] [2]alerting_test.go,istio_test.go,cis_benchmark_test.go,logging_test.go,monitoring_test.go,neuvector_test.go,public_gitrepo_test.go,upgrade_test.go,installation_test.go,longhorn_test.go,network_policy_test.go,port_test.go,neuvector_hardened_test.go,workload_test.go,workload_test.goin multiple directories) to include the newpit.elementaltag, ensuring these tests are executed for Elemental environments. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16]Test suite definition cleanup:
elemental_schemas.yamlfile, which previously defined the Elemental test suite and individual test cases, likely in favor of the new tag-based test selection.