Scenario Testing
aiskillstore/marketplace
This skill should be used when writing tests, validating features, or needing to verify code works.
Migrate an oc-mirror e2e test case to the integration test suite, translating framework, registry, invocation, and assertion patterns
Install Migrate E2E To Integration
$ npx skills add openshift/oc-mirror --skill migrate-e2e-to-integration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift/oc-mirror migrate-e2e-to-integration --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openshift/oc-mirror.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/migrate-e2e-to-integration .claude/skills/migrate-e2e-to-integration && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "migrate-e2e-to-integration" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/migrate-e2e-to-integration into .claude/skills/migrate-e2e-to-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-e2e-to-integration", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openshift/oc-mirror/tree/main/.agents/skills/migrate-e2e-to-integrationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openshift/oc-mirror --skill migrate-e2e-to-integration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift/oc-mirror migrate-e2e-to-integration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift/oc-mirror.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/migrate-e2e-to-integration .agents/skills/migrate-e2e-to-integration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "migrate-e2e-to-integration" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/migrate-e2e-to-integration into .agents/skills/migrate-e2e-to-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-e2e-to-integration", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift/oc-mirror --skill migrate-e2e-to-integration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift/oc-mirror migrate-e2e-to-integration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift/oc-mirror.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/migrate-e2e-to-integration .cursor/skills/migrate-e2e-to-integration && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "migrate-e2e-to-integration" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/migrate-e2e-to-integration into .cursor/skills/migrate-e2e-to-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-e2e-to-integration", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openshift/oc-mirror.git --path .agents/skills/migrate-e2e-to-integration--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openshift/oc-mirror --skill migrate-e2e-to-integration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift/oc-mirror migrate-e2e-to-integration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift/oc-mirror.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/migrate-e2e-to-integration .gemini/skills/migrate-e2e-to-integration && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "migrate-e2e-to-integration" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/migrate-e2e-to-integration into .gemini/skills/migrate-e2e-to-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-e2e-to-integration", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openshift/oc-mirror migrate-e2e-to-integrationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openshift/oc-mirror --skill migrate-e2e-to-integration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openshift/oc-mirror.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/migrate-e2e-to-integration .github/skills/migrate-e2e-to-integration && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "migrate-e2e-to-integration" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/migrate-e2e-to-integration into .github/skills/migrate-e2e-to-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-e2e-to-integration", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift/oc-mirror --skill migrate-e2e-to-integration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openshift/oc-mirror migrate-e2e-to-integration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift/oc-mirror.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/migrate-e2e-to-integration .opencode/skills/migrate-e2e-to-integration && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "migrate-e2e-to-integration" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/migrate-e2e-to-integration into .opencode/skills/migrate-e2e-to-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-e2e-to-integration", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
migrate-e2e-to-integration- GitHub stars
- 124
- Token cost
- ~1.5k tokens
- SKILL.md length
- 688 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Migrate an oc-mirror e2e test case to the integration test suite, translating framework, registry, invocation, and assertion patterns
- Works in 9 steps: Read project conventions → Locate and analyze the e2e test case → Check for existing integration coverage → …
- Tasks that involve End-to-end testing
- SKILL.md covers Input and Step-by-step process
- Calls go
What it does
Migrate E2E To Integration is an agent skill from openshift/oc-mirror. Migrate an oc-mirror e2e test case to the integration test suite, translating framework, registry, invocation, and assertion patterns
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering End-to-end testing, Test generation and Integration testing. The repository describes itself as: Lifecycle manager for internet-disconnected OpenShift environments. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve End-to-end testing
- Tasks that involve Test generation
- Tasks that involve Integration testing
Example prompts
- “/migrate-e2e-to-integration”
Workflow steps
9 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 873d7db. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
go
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Migrate E2E To Integration loads about 1.5k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 688 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from openshift/oc-mirror at commit 873d7db, republished under its Apache-2.0 licence (© openshift). 688 words, ~1,525 tokens.
Download SKILL.mdSave it as
.claude/skills/migrate-e2e-to-integration/SKILL.md (or your agent's skills folder).- name
- migrate-e2e-to-integration
- description
- Migrate an oc-mirror e2e test case to the integration test suite, translating framework, registry, invocation, and assertion patterns
- user-invocable
- true
Migrate E2E Test Case to Integration
Convert an existing e2e test case from tests/e2e/test/e2e/oc_mirror_v2.go into an integration test under tests/integration/.
Input
The user provides one of:
- An e2e case number (e.g., 72973)
- A test description or keyword
Step-by-step process
1. Read project conventions
Read AGENTS.md at the project root, and the documents at docs/testing for architecture, conventions, and pitfalls.
2. Locate and analyze the e2e test case
Search tests/e2e/test/e2e/oc_mirror_v2.go for the case number or description. Extract:
- What scenario it tests (workflow, flags, edge case)
- How oc-mirror is invoked (subcommand, flags, config)
- What it asserts (images mirrored, files created, errors expected)
- What test data config it uses (from
tests/e2e/test/e2e/testdata/)
Do not attempt a 1:1 translation of the test case, consider if it makes sense at a high level, if it's already covered at the integration or unit levels, if the assertions are sound, if it could be made more efficient, etc.
3. Check for existing integration coverage
Read integration test files in tests/integration/ to verify the scenario isn't already covered. If it is, tell the user and suggest what additional value the e2e case provides, if any.
4. Present the migration plan
Before writing any code, present a detailed plan to the user and wait for approval. The plan must include:
- E2E summary: What the original test does — scenario, flags, config, assertions.
- Translation approach: How each part maps to integration patterns (runner method, assertion helpers, test structure). Call out anything that won't translate 1:1 and explain why.
- Test data: Which existing ISC/DISC configs will be reused, and whether new ones are needed.
- Target file: Where the new test will live and why (existing file vs new file).
- Assertion coverage: List every assertion from the e2e case and the corresponding integration check. Flag any assertions that will be dropped or changed, with justification.
- Improvements: Any improvements over the original (removing unnecessary polling, better assertions, broader coverage, etc.).
Do not proceed to implementation until the user approves the plan. If the user requests changes, revise and re-present.
5. Translate the test
Apply these conversions:
Registry setup
- E2E: Manual pod deployment via
createregistry(), TLS trust viatrustCert(), pull secret extraction. - Integration: Use the suite's
testRegistryglobal — it's started inBeforeEachand stopped inAfterEachautomatically. No TLS or pull secret setup needed.
oc-mirror invocation
- E2E:
oc.WithoutNamespace().WithoutKubeconf().Run("mirror").Args(...)with manual flag construction. - Integration: Use
runnermethods fromtests/integration/pkg/ocmirror/:runner.MirrorToMirror(ctx, iscPath, workDir, registryEndpoint, ...extraFlags)runner.MirrorToDisk(ctx, iscPath, workDir, ...extraFlags)runner.DiskToMirror(ctx, iscPath, workDir, registryEndpoint, ...extraFlags)runner.DeletePhaseOne(ctx, discPath, workDir, registryEndpoint, ...extraFlags)runner.DeletePhaseTwo(ctx, deleteYaml, registryEndpoint, ...extraFlags)runner.ListOperators(ctx, ...args)runner.ListReleases(ctx, ...args)
Show full SKILL.md (269 more words)Show less
Polling and retries
- E2E: Uses
wait.Poll()and manual retry loops. - Integration: Remove all polling — integration calls are synchronous. The runner returns when oc-mirror exits.
Assertions
- E2E: Raw
o.Expect(...)on command output, manual image inspection. - Integration: Use helpers from
tests/integration/helpers_test.go:expectOcMirrorCommandSuccess(result, err)expectSuccessfulMirrorInRegistry(iscPath, registry)expectCorrectIDMS(workDir, iscPath)expectValidDeleteImagesFiles(workDir, deleteID)expectEmptyRegistry(registry)- Follow the
expect*naming pattern for any new helpers.
Test images
- E2E: Often uses real release images and production operator catalogs.
- Integration: Use the self-hosted test images:
- Catalog:
quay.io/oc-mirror/oc-mirror-dev:test-catalog-latest - Release:
quay.io/oc-mirror/release/test-release-index:v0.0.1 - Additional:
quay.io/openshifttest/hello-openshift@sha256:61b8f5...
- Catalog:
Test data configs
- Check existing ISC/DISC configs in
tests/integration/testdata/imagesetconfigs/first. - Only create new ones if the scenario needs a config that doesn't exist.
- Use test images (above) instead of production images.
6. Write the integration test
Follow the automate-integration-test skill for the writing conventions:
- Read
tests/integration/integration_suite_test.goandtests/integration/helpers_test.gofor current patterns - Use Ginkgo v2 structure:
Describe/Context/It/By - Place the test in the appropriate existing file, or create a new one if it's a new category
- Every line should earn its place — no superfluous comments, unused variables, or boilerplate
7. Review the code
Before running, verify:
- Assertions actually test what the e2e case tested — don't lose coverage in the translation
- No e2e-specific patterns leaked in (manual polling, cluster assumptions, production images)
- Helpers are reused where possible
8. Run the test
Ask permission, then run:
PATH=$PATH:<path-to-registry-bin> go test -v ./tests/integration/ --ginkgo.focus "<test label>"9. Recommend e2e disposition
After the integration test passes, advise the user:
- Remove the e2e case if it doesn't exercise anything cluster-specific (most common)
- Keep the e2e case if it tests cluster-level behavior (IDMS application, node reboot, operator deployment to a real cluster)
- Keep both temporarily if unsure, with a note to revisit
© openshift, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/migrate-e2e-to-integration of openshift/oc-mirror.
Open the folder on GitHubat commit 873d7db
Compare with similar skills
Migrate E2E To Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Migrate E2E To Integration this skillopenshift/oc-mirror | 124 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Scenario Testingaiskillstore/marketplace | 430 | 1 repos | ~830 | Automated safety check: Pass | None | |
| Con CLI E2Enowledge-co/con-terminal | 625 | — | ~1.2k | Automated safety check: Pass | MIT | |
| PR TestElite588/AUTOGPT | 103 | — | ~9.4k | Automated safety check: Notes | Custom licence | |
| Testing Strategiesancoleman/ai-design-components | 526 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Coveryonatangross/orchestkit | 289 | — | ~6.3k | Automated safety check: Notes | MIT |
Similar skills
Con CLI E2E
nowledge-co/con-terminal
Validate Con's local socket control plane against a real running app session, and write/run con-test integration tests.
PR Test
Elite588/AUTOGPT
E2E manual testing of PRs/branches using docker compose, agent-browser, and API calls.
Testing Strategies
ancoleman/ai-design-components
Strategic guidance for choosing and implementing testing approaches across the test pyramid.
Cover
yonatangross/orchestkit
Generate tests that do not exist yet. An agent skill from yonatangross/orchestkit.
Playwright Test
AI-Unified-Process/marketplace
Creates Playwright browser-based tests for Vaadin views using the Drama Finder library for type-safe element wrappers with accessibility-first APIs.
More from openshift/oc-mirror
Automate Integration Test
openshift/oc-mirror
Convert a manual test case description into a Ginkgo oc-v2 integration test for oc-mirror
Check Test Coverage
openshift/oc-mirror
Analyze oc-mirror CLI feature coverage across integration and e2e tests, identifying untested features and gaps
Related
Categories
Questions about Migrate E2E To Integration
What does Migrate E2E To Integration do?
Migrate an oc-mirror e2e test case to the integration test suite, translating framework, registry, invocation, and assertion patterns. Migrate E2E To Integration is an agent skill from openshift/oc-mirror.
When should I use Migrate E2E To Integration?
Migrate E2E To Integration fits situations like: tasks that involve End-to-end testing; tasks that involve Test generation; tasks that involve Integration testing.
How do I install Migrate E2E To Integration in Claude Code?
Run `npx skills add openshift/oc-mirror --skill migrate-e2e-to-integration -a claude-code`. Or copy the skill folder (.agents/skills/migrate-e2e-to-integration in openshift/oc-mirror) into .claude/skills/migrate-e2e-to-integration in your project. Claude Code loads it when a task matches its description.
How do I install Migrate E2E To Integration in Codex?
Run `npx skills add openshift/oc-mirror --skill migrate-e2e-to-integration -a codex`. Or copy the skill folder (.agents/skills/migrate-e2e-to-integration in openshift/oc-mirror) into .agents/skills/migrate-e2e-to-integration in your project. Codex loads it when a task matches its description.
Can I use Migrate E2E To Integration in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openshift/oc-mirror --skill migrate-e2e-to-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/migrate-e2e-to-integration, .gemini/skills/migrate-e2e-to-integration, .github/skills/migrate-e2e-to-integration and .opencode/skills/migrate-e2e-to-integration in your project.
What does Migrate E2E To Integration need to run?
Going by SKILL.md and its folder, Migrate E2E To Integration needs the command-line tools its instructions call (go).
Does Migrate E2E To Integration access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Migrate E2E To Integration safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Migrate E2E To Integration use?
Migrate E2E To Integration is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Migrate E2E To Integration use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Migrate E2E To Integration?
Skills that share tags, products or a category with Migrate E2E To Integration: Scenario Testing (aiskillstore/marketplace, 430 stars), Con CLI E2E (nowledge-co/con-terminal, 625 stars), PR Test (Elite588/AUTOGPT, 103 stars) and Testing Strategies (ancoleman/ai-design-components, 526 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Migrate E2E To Integration?
openshift (a GitHub organization) maintains it in openshift/oc-mirror, which has 124 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.
Source: openshift/oc-mirror on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.