Testing & Verification Workflows

Workflows for designing, generating, and porting test harnesses. Covers verification surface design through engine activation and cross-framework test porting.

How to Start

• “Design a test harness for this component” → test_harness_authoring.00_system_survey_classification

• “Port our pytest tests to the TOML harness” → test_harness_porting.00_harness_inventory_audit

Test Harness Authoring

Design and build a verification harness from scratch.

Step	Skill	What it does
0	test_harness_authoring.00_system_survey_classification	Survey the system and classify testable surfaces
1	test_harness_authoring.01_verification_surface_design	Design verification surfaces and test boundaries
2	test_harness_authoring.02_verification_surface_review	Review surface design for gaps and feasibility
3	test_harness_authoring.03_definition_generation	Generate TOML test definitions
4	test_harness_authoring.04_definition_feasibility_validation	Validate definitions against real infrastructure
5	test_harness_authoring.05_engine_activation	Activate definitions in the proof harness engine

Test Harness Porting

Port an existing test framework to Apogee’s TOML harness format.

Step	Skill	What it does
0	test_harness_porting.00_harness_inventory_audit	Audit existing test infrastructure
1	test_harness_porting.01_taxonomy_mapping_review	Map existing test taxonomy to TOML schema
2	test_harness_porting.02_definition_generation	Generate TOML definitions from existing tests
3	test_harness_porting.03_gating_parity_validation	Validate gating parity with original framework
4	test_harness_porting.04_execution_parity_verification	Verify execution produces equivalent results
5	test_harness_porting.05_cutover	Cut over to the new harness

See Also

• apogee-proof — the TOML-driven proof harness engine

• Glossary — proof depth, proof harness terminology