fire-test

/fire-test - Dominion Flow Integration Tests

Purpose

Run the Dominion Flow plugin test suite to verify all commands and integrations work correctly. Provides comprehensive validation of the entire plugin ecosystem before deployment or after updates.

Usage

/fire-test                      # Run all tests (E2E + Integration)
/fire-test --e2e                # Run E2E tests only (8 tests)
/fire-test --integration        # Run integration tests only (3 tests)
/fire-test --command [name]     # Test specific command (e.g., fire-1-new)

Test Suites

E2E Tests (8 tests)

End-to-end tests verify each command works in isolation:

Test	Command	Verification
1	/fire-1a-new	Creates correct .planning/ structure with all required files
2	/fire-2-plan	Generates valid BLUEPRINT.md with skills references and must-haves
3	/fire-3-execute	Completes breath execution with RECORD.md output
4	/fire-4-verify	Runs all Must-Haves + WARRIOR validation checks
5	/fire-5-handoff	Creates unified fire-handoff.md with 7-step format
6	/fire-6-resume	Restores full context from handoff file
7	/fire-search	Finds relevant skills from library by query
8	/fire-contribute	Adds new skill to library with proper structure

Integration Tests (3 tests)

Integration tests verify cross-component functionality:

Test	Scenario	Verification
1	Full Workflow	Complete cycle: new -> plan -> execute -> verify -> handoff -> resume
2	Skills Sync	Bidirectional sync between project and global skills library
3	Hooks	SessionStart hook fires and injects context correctly

Test Execution Process

Step 1: Parse Arguments
├── Check for --e2e, --integration, or --command flags
├── Determine which test suite(s) to run
└── Validate command name if --command specified

Step 2: Create Temp Test Directory
├── Create isolated test directory: $TEMP/dominion-flow-test-{timestamp}/
├── Initialize minimal project structure
├── Copy test fixtures from tests/fixtures/
└── Set up clean environment variables

Step 3: Run Selected Test Suite(s)
├── E2E Tests:
│   ├── For each command test:
│   │   ├── Execute command in test directory
│   │   ├── Verify expected outputs exist
│   │   ├── Validate file contents/structure
│   │   └── Record pass/fail status
│   └── Aggregate E2E results
│
├── Integration Tests:
│   ├── Full workflow test:
│   │   ├── Run complete workflow sequence
│   │   ├── Verify state transitions
│   │   └── Check final artifacts
│   ├── Skills sync test:
│   │   ├── Create test skill locally
│   │   ├── Sync to global library
│   │   ├── Verify bidirectional sync
│   │   └── Clean up test skills
│   └── Hooks test:
│       ├── Trigger SessionStart event
│       ├── Verify context injection
│       └── Check hook output
│
└── Command-specific test (if --command used):
    ├── Run only the specified command test
    └── Provide detailed output

Step 4: Capture Results
├── Collect pass/fail for each test
├── Capture any error messages
├── Record execution times
└── Note any warnings or skipped tests

Step 5: Generate Test Report
├── Create formatted report (see format below)
├── Calculate totals and percentages
├── Highlight failures with details
└── Provide recommendations for fixes

Step 6: Clean Up
├── Remove temp test directory
├── Restore any modified global state
└── Clear test environment variables

Step 7: Return Status
├── Exit 0 if all tests passed
├── Exit 1 if any tests failed
└── Display summary message