qa-testing

QA Testing Skill

Execute scenario-based QA testing driven by docs/qa/**/*.md documents.

Prerequisites

CRITICAL: Always rebuild CLI before testing to ensure you have the latest version.

1. Rebuild CLI (REQUIRED - ensures latest code):

   cargo build --release -p orchestrator-cli -p orchestratord
   

2. Initialize orchestrator if needed — only when the database does not exist yet:

   # `orchestrator init` is only for a genuinely absent runtime database.
   # The default runtime root is ~/.orchestratord; ORCHESTRATORD_DATA_DIR overrides it.
   orchestrator daemon status
   

3. For QA scenario isolation — use project-scoped reset instead of destroying shared state:

   # Delete a project's state (task data + config + auto-tickets)
   orchestrator delete project/<project> --force
   # Deploy fixtures into project scope (other projects untouched)
   orchestrator apply -f fixtures/manifests/bundles/<fixture>.yaml --project <project>
   

4. QA docs exist under docs/qa/.

5. Optional: UI automation via browser tools.

Conventions / Configuration

API helper script: .claude/skills/tools/qa-api-test.sh

Environment variables:

• API_BASE_URL (default: http://localhost:8080)
• API_TOKEN (optional)
• API_TOKEN_CMD (optional command that prints a token to stdout)

Notes:

• If the API does not require auth, omit API_TOKEN and API_TOKEN_CMD.
• If the API requires auth, prefer providing a project-specific API_TOKEN_CMD (for example, a script under scripts/).

Test Scripts Directory (scripts/qa/)

IMPORTANT: A collection of reusable QA test scripts may exist in scripts/qa/. Before writing any new test script, always check scripts/qa/ first for an existing script that covers the same or similar scenario.

• Reuse first: Run ls scripts/qa/ or Glob: scripts/qa/* to find existing scripts. If a matching script exists, use it directly (or adapt it) instead of creating a new one.
• Create in scripts/qa/: When a new test script is needed, always place it under scripts/qa/ — never in the project root or other ad-hoc locations.
• Naming convention: Follow existing patterns — e.g., test-{feature}.{js,mjs,py,sh} or {feature}_test.py.