Ln 630 Test Auditor

What it does

The Ln 630 Test Auditor skill is an L2 Coordinator designed to analyze test data according to ln-630 standards. It identifies discrepancies within business logic, end-to-end priority, value, coverage, isolation, manual tests, and structure, and suggests remediation steps for improved quality. The coordinator orchestrates a series of specialized audit workers (ln-631 through ln-637) to perform these analyses.

When to use it

This skill is useful in the following scenarios:

• When needing to assess the overall health and effectiveness of automated and manual test suites.
• To ensure business logic, end-to-end priorities, value delivery, code coverage, isolation, and test structure adhere to best practices.
• For identifying gaps or weaknesses in existing testing processes.
• As part of a risk-based testing approach.
• When needing to generate comprehensive audit reports with aggregated findings.

Key capabilities

• Coordination of Specialized Workers: Delegates tasks to workers such as ln-631-test-business-logic-auditor, ln-632-test-e2e-priority-auditor, and others for focused audits.
• Audit Scope Definition & Manifest Creation: Defines the scope of the audit and builds a manifest to guide the process.
• Research Integration: Incorporates current testing best practices research into the auditing workflow.
• Report Generation: Generates an aggregate audit report summarizing findings from all delegated workers.
• Runtime Contract Adherence: Operates within the evaluation-runtime framework and follows defined phases (CONFIG, DISCOVERY, RESEARCH, DELEGATE, AGGREGATE, REPORT, SELF_CHECK).

Example prompts

Here are some examples of how to invoke this skill:

• Skill(skill: "ln-631-test-business-logic-auditor", args: "{scope}")
• Skill(skill: "ln-632-test-e2e-priority-auditor", args: "{scope}")
• Skill(skill: "ln-634-test-coverage-auditor", args: "{scope}")

Tips & gotchas

• Mandatory Reads: Before using this skill, it is mandatory to review the referenced documents located in shared/references/. These include contracts for evaluation coordination and risk-based testing guides.
• Worker Delegation: The coordinator should use the Skill tool for delegated workers; do not attempt to inline worker logic directly within the coordinator itself.
• TodoWrite Format: All outputs must adhere to the TodoWrite format as specified in the documentation.