Run all tests (unit, integration, E2E) in isolated containers separate from dev environment. Handles build, container startup, health checks, test execution, and cleanup. SINGLE SOURCE OF TRUTH for running tests in isolated containers.
Runs all tests in isolated containers with fresh databases, handling build, startup, health checks, and cleanup. Use this before any test execution to prevent interference with dev environment and ensure complete test isolation.
/plugin marketplace add DarkMonkDev/WitchCityRope/plugin install darkmonkdev-witchcityrope-agents@DarkMonkDev/WitchCityRopeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Purpose: Run all tests in isolated containers separate from dev environment
When to Use:
Single Source: This skill is the ONLY way to run tests in isolated containers.
✅ Complete Isolation
witchcityrope_test)✅ Fresh Environment
✅ All Test Types
✅ Automatic Cleanup
# Run E2E tests (default)
bash .claude/skills/test-environment/execute.sh
# Run specific E2E test file
bash .claude/skills/test-environment/execute.sh --mode e2e --filter "admin-events-dashboard"
# Run all tests
bash .claude/skills/test-environment/execute.sh --mode all
# Keep containers for debugging
bash .claude/skills/test-environment/execute.sh --mode e2e --keep-containers
| Option | Description |
|---|---|
--mode MODE | Test mode: all, unit, integration, e2e, failed-only |
--filter PATTERN | Filter E2E tests by filename pattern |
--coverage | Generate coverage reports (not yet implemented) |
--keep-images | Keep built images for faster reruns |
--keep-containers | Keep containers running for debugging |
--skip-confirm | Skip confirmation prompts (for automation) |
--mode e2e (default)Runs Playwright E2E tests against test containers.
--mode allRuns all test types: unit + integration + e2e
--mode unitRuns .NET unit tests only
--mode integrationRuns .NET integration tests only
--mode failed-onlyReruns previously failed tests (not yet implemented)
BEFORE running ANY tests:
1. Use test-environment skill to start isolated containers
2. Skill handles build, start, health checks automatically
3. Run tests in isolation
When writing/debugging tests:
1. Use test-environment skill with --keep-containers
2. Inspect running containers for debugging
3. Containers remain running until manual cleanup
.claude/skills/test-environment/
├── SKILL.md # This file
├── execute.sh # Main entry point
├── lib/
│ ├── build-containers.sh # Build test images
│ ├── start-containers.sh # Start test containers
│ ├── run-tests.sh # Execute tests
│ ├── health-checks.sh # Verify environment
│ ├── cleanup.sh # Remove containers/images
│ └── failed-tests-tracker.sh # Track failures (TODO)
└── config/
└── test-modes.json # Test mode configurations
Build fails: Check for compilation errors in source code
Health check fails: Review container logs with docker logs
Tests fail: Results saved to /test-results/
Orphaned images: Skill automatically prunes on cleanup
Last Updated: 2025-12-02 Maintained by: Test Team Related: test-executor-lessons-learned.md, test-developer-lessons-learned.md
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.