integration-test-runner

To run integration checks on design-docs pipeline outputs, execute the canonical integration harness and compare the actual ARTICLES array, chart bindings, and brand sections against the repository. Provide the required configPath, chartDataPath, and articleDetailPagePath inputs to validate per-article structure.

Design-docs pipeline validation checks per-article structure, fonts, colors, charts, and brand sections. It enforces defined test categories, cross-article rules, and brand validations by comparing the actual ARTICLES array and generated outputs against the repository.

To validate chart data bindings in an integration test harness, execute the design-docs pipeline verification workflow using the chartDataPath input. The harness compares actual chart and data bindings against the repository to ensure fidelity with canonical implementations.

Yes, you need specific file paths to execute the design-docs integration harness. The required inputs are configPath, chartDataPath, and articleDetailPagePath. These file paths allow the harness to locate and validate the generated outputs against the repository.

You should run integration tests for the design-docs pipeline during the verification workflow, specifically Step 7. This step triggers after audit-responsive-accessibility to validate per-article structure, fonts, colors, charts, and brand sections against canonical implementations.

Your design-docs integration test fails on brand sections when the actual generated outputs do not match the cross-article rules and brand validations defined in the repository. The harness enforces these specific test categories to ensure compatibility with canonical implementations.