smaqit-test-start

name	smaqit.test-start
description	Start testing session with focused context. Use when beginning test workflows with the user-testing agent.
metadata	{"version":"0.3.1"}
agent	smaqit.user-testing

Test Start

Start a testing session with minimal, focused context. Loads project test entrypoints and (optionally) a specific test file only.

Steps

Execute these steps IN ORDER:

1. Load Test Entry Points (Parallel)

Read the project files that define how tests are run (whichever exist):

• README.md
• CONTRIBUTING.md and/or TESTING.md
• Makefile
• package.json (scripts)
• pyproject.toml / tox.ini / pytest.ini
• go.mod (then infer go test ./...)

Critical: Read complete files without truncation.

2. Load Specific Test File

User must specify: Test number (e.g., "059")

Read the complete test file:

• .smaqit/user-testing/tests/{TEST_NUMBER}_*.md

If the test file does not exist, ask whether to create it by invoking smaqit.test-create before proceeding.

This file contains:

• Test objectives
• Phase-by-phase workflow
• Validation checkpoints
• Success criteria
• Issue-specific validation points

3. Understand Test Context

From the test file, identify:

• Test type (e2e, regression, integration, unit)
• Issues being validated (list of specific issues with fix references)
• Critical checkpoints (where failures are most likely)
• Evidence requirements (what to collect for report)
• Pass/fail criteria (what determines success)

4. Confirm Ready State

Present a concise summary:

• Test file loaded: {TEST_NUMBER}
• Test type: {TYPE}
• Issues to validate: {COUNT} issues
• Estimated duration: {DURATION}
• Critical checkpoints: {COUNT}

Then state: "Ready to begin test execution. Say 'start' to proceed."

What This Does NOT Load

Explicitly excluded to keep context focused:

• ❌ History files (.smaqit/history/*.md) - Not needed for test execution
• ❌ Task planning (.smaqit/PLANNING.md) - Not needed during test
• ❌ Other test files - Only the specific test file is loaded
• ❌ Previous test reports - Each test is independent

What This DOES Load

Minimal focused context:

• ✅ Test entrypoints (project-specific) - How to run the test suite
• ✅ Specific test file (optional) - If provided, follow its workflow and criteria

Critical Requirements

READ COMPLETE FILES: Do NOT truncate test entrypoint files or the test file.

MODE: You are now in test execution mode. Follow the test file workflow and your agent directives for execution philosophy, coordination patterns, and report generation.

Success Criteria

Test start is successful when:

• Test entrypoint files read completely
• Specific test file read completely (if provided)
• Test type and objectives understood
• Issue list and validation points identified
• Critical checkpoints mapped to workflow phases
• Evidence requirements clear
• Pass/fail criteria understood
• Ready state confirmed to user