Agent skill
test:run-hypershift
Run E2E tests on HyperShift cluster
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/test-run-hypershift
SKILL.md
Run Tests on HyperShift
Auto-approved: All test execution on hosted HyperShift clusters is auto-approved.
When to Use
- Running full E2E tests including MLflow, Phoenix, auth
- Validating before merging to main
- Testing OpenShift-specific features
Run All Tests
KUBECONFIG=~/clusters/hcp/kagenti-hypershift-custom-$CLUSTER/auth/kubeconfig \
./.github/scripts/local-setup/hypershift-full-test.sh $CLUSTER --include-test
Run Specific Tests
KUBECONFIG=~/clusters/hcp/kagenti-hypershift-custom-$CLUSTER/auth/kubeconfig \
./.github/scripts/local-setup/hypershift-full-test.sh $CLUSTER \
--include-test --pytest-filter "test_agent or test_mlflow"
Run from Worktree
KUBECONFIG=~/clusters/hcp/kagenti-hypershift-custom-$CLUSTER/auth/kubeconfig \
.worktrees/$WORKTREE/.github/scripts/local-setup/hypershift-full-test.sh $CLUSTER \
--include-test --pytest-filter "test_agent"
Test Categories
| Filter | Tests | Notes |
|---|---|---|
test_agent |
Agent conversation tests | Needs LLM (OpenAI) |
test_mlflow |
MLflow traces, auth | HyperShift only |
test_agent or test_mlflow |
Both (recommended) | Traces need fresh agent calls |
Related Skills
test:run-kind- Run on Kind (faster, no MLflow)test:review- Review test qualitytdd:hypershift- Full TDD loop on HyperShifthypershift:cluster- Create cluster if needed
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?