Test Collaboration Governance

When to Activate

• Inventorying test assets, test gaps, or the standard test entry point.
• Giving a requirement, business rule, risk, or important defect durable verification evidence.
• Enabling frontend/backend or multiple services to develop and test independently against one machine-readable contract.

Anti-Patterns

• Mirroring every test function or copying business success criteria into the registry.
• Treating test count, file existence, or green CI as sufficient behavioral evidence.
• Deleting, weakening, or quarantining tests merely to get green without recording the risk and an explicit manual exit.

Related Skills