📖 [Docs]: Test instructions updated to document per-test-file repository model#598
Merged
Marius Storhaug (MariusStorhaug) merged 1 commit intomainfrom May 3, 2026
Conversation
Contributor
No Significant Changes DetectedThis PR does not contain changes to files that would trigger a new release:
Build, test, and publish stages will be skipped for this PR. If you believe this is incorrect, please verify that your changes are in the correct locations. |
Contributor
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
May 3, 2026 11:15
View session
Contributor
There was a problem hiding this comment.
Pull request overview
This docs-only PR updates the integration test instructions to describe a per-test-file repository model and a self-contained test lifecycle for files under tests/. The goal is to guide contributors and automation toward better test isolation during parallel runs.
Changes:
- Updates the instruction frontmatter and setup/teardown guidance to describe per-test-file repository ownership.
- Rewrites the example test-file structure to show repo provisioning plus stale-resource cleanup/teardown responsibilities.
- Replaces the repository naming rules and key rules with
{TestName}-{OS}-{TokenType}-{RunID}-based guidance.
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.
Test instructions now document the per-test-file repository model — each test file owns its own repository, handles idempotent setup, cleans stale resources, and tears down after itself. Contributors following the instructions will correctly scope their tests to avoid cross-file interference during parallel execution.
Changed: Repository naming and ownership model
The instructions previously described a shared
Test-{OS}-{TokenType}-{RunID}repository used by all test files. Each test file now owns its own repository using the pattern{TestName}-{OS}-{TokenType}-{RunID}, preventing resource collisions when tests run in parallel across OS matrices.{TestName}-{OS}-{TokenType}-{RunID}Releases-Linux-USER_FG_PAT-1234{TestName}-{OS}-{TokenType}-{RunID}-{N}Secrets-Linux-ORG_FG_PAT-1234-2New: Self-containment principle
Each test file is now documented as fully self-contained:
BeforeAllensures the test repository exists (idempotent creation) and cleans stale resources from prior runs with the sameGITHUB_RUN_IDAfterAlltears down all test-specific resourcesTechnical Details
.github/instructions/tests.instructions.md