# Test Execution

> Invoke when test-executor runs tests and reports results. Provides progressive execution strategy (unit then integration then system then e2e), environment verification checklists, Docker test patterns, and structured result summary with next-step recommendations.

- Skill: `masanao-ohba/test-execution` (Agent Skill)
- Install (CLI): `npx skillmds@latest add masanao-ohba/test-execution`
- Raw SKILL.md: https://api.skillmd.com/api/skills/masanao-ohba/test-execution/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: masanao-ohba (https://skillmd.com/u/masanao-ohba)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/masanao-ohba/test-execution

---


# Test Execution

A technology-agnostic skill for test execution strategy, environment management, and result reporting.

## Execution Strategy

```yaml
strategy: progressive_execution
description: "Run tests in order of feedback speed"

phases:
  1_unit_tests:
    description: "Fast, isolated tests"
    run_first: true
    fail_fast: true
    typical_duration: "seconds"

  2_integration_tests:
    description: "Component interaction tests"
    run_if: "Unit tests pass"
    fail_fast: false
    typical_duration: "seconds to minutes"

  3_system_tests:
    description: "Full system tests"
    run_if: "Integration tests pass"
    fail_fast: false
    typical_duration: "minutes"

  4_e2e_tests:
    description: "End-to-end user flows"
    run_if: "System tests pass"
    fail_fast: false
    typical_duration: "minutes to hours"
```

## Test Selection

```yaml
selection_patterns:
  changed_files:
    description: "Run tests affected by changes"
    approach:
      - "Identify modified files"
      - "Find tests that import/use those files"
      - "Run only affected tests"

  smoke_tests:
    description: "Critical path verification"
    use_when: "Quick validation needed"
    coverage: "Core functionality only"

  full_suite:
    description: "All tests"
    use_when:
      - "Pre-merge validation"
      - "Release preparation"
      - "Periodic verification"
```

## Environment Management

### Environment Verification

```yaml
environment_checks:
  pre_execution:
    - "Test database accessible?"
    - "Required services running?"
    - "Environment variables set?"
    - "Test fixtures available?"

  isolation:
    - "Tests don't share state?"
    - "Database reset between tests?"
    - "No external side effects?"

  cleanup:
    - "Test data removed after run?"
    - "Temporary files deleted?"
    - "Mock servers stopped?"
```

### Docker Test Environment

```yaml
docker_patterns:
  compose_test:
    description: "Use docker-compose for test environment"
    structure:
      - "docker-compose.test.yml"
      - "Test-specific configuration"
      - "Isolated network"

  commands:
    full_run: "docker compose -f docker-compose.test.yml up --abort-on-container-exit"
    specific: "TEST_ONLY=<path> docker compose -f docker-compose.test.yml up"
    cleanup: "docker compose -f docker-compose.test.yml down -v"
```

## Result Summary Format

```yaml
result_summary:
  overview:
    total: <number>
    passed: <number>
    failed: <number>
    errors: <number>
    skipped: <number>
    duration: <seconds>

  failure_details:
    - test: "<test name>"
      type: "ERROR|FAILURE"
      message: "<error message>"
      location: "<file:line>"

  next_steps:
    - action: "<what to do>"
      reason: "<why>"
      priority: "high|medium|low"
```

## Reporting

### Report Structure

```yaml
report_structure:
  summary:
    - "Pass/fail ratio"
    - "Duration"
    - "Coverage (if available)"

  failures:
    - "Grouped by category"
    - "Ordered by priority"
    - "With actionable context"

  next_steps:
    - "Specific actions to take"
    - "Which agent should handle"
    - "Estimated complexity"
```

## Used By Agents

```yaml
primary_users:
  - test-executor: "Test execution and result reporting"
```