test-execution

Test Execution

Goal

Execute confirmed test cases and record evidence by priority.

Required Inputs

• Confirmed module artifact directory.
• Readable 01-04 planning artifacts.
• Final execution plan from execution-gate.
• Confirmed risk boundary.
• Runtime dependency check result from execution-gate, including downgrade strategy for unavailable optional dependencies.

Execution Modes

Single-agent mode:

• Execute P0 -> P1 -> P2 -> P3.
• Write each priority result to its own 执行结果/Px/ directory.
• Each priority directory must contain priority-owned 05-执行记录.md and 06-缺陷记录.md, plus screenshots/, videos/, and scripts/.

Multi-agent mode:

• Dispatch by priority only.
• A child agent writes only its assigned 执行结果/Px/ directory.
• Each assigned priority directory must contain priority-owned 05-执行记录.md and 06-缺陷记录.md, plus screenshots/, videos/, and scripts/.
• Child agents do not modify 01-04.
• Child agents do not write root 05-执行记录.md or 06-缺陷记录.md.

Priority Directory Contract

For every executed priority, use this structure:

执行结果/Px/
执行结果/Px/05-执行记录.md
执行结果/Px/06-缺陷记录.md
执行结果/Px/screenshots/
执行结果/Px/videos/
执行结果/Px/scripts/

Root 05-执行记录.md and 06-缺陷记录.md are generated by result-aggregation from these priority-owned files.

First-Run Browser Protocol

Before the first browser navigation for each page or key flow, read and apply browser-execution-protocol.md. Use it again when a browser recheck enters an unknown page state.

• Match reconnaissance to static HTML or a dynamic application.
• Complete the enter, readiness, reconnaissance, locator, action, assertion, classification, evidence, and cleanup loop.
• Keep observable readiness conditions, runtime observation, locator risk, and resource ownership explicit in the priority execution record.
• Preserve the backend and diagnostic escalation rules below; the protocol standardizes execution behavior and does not replace the confirmed backend.