testing--auditing

Audit automated test suites to surface coverage gaps, weak oracles, and determinism shortfalls. By analyzing public entry points and changed symbols, the assessment maps guarantees and gaps to output a structured inventory and risk-weighted guidance for safer releases.

Weak oracles are test assertions that provide insufficient validation guarantees. Identify them by auditing existing tests against implementation behavior to distinguish strong versus weak oracles, ensuring boundaries are tested and coverage gaps are mapped to specific risk tiers.

Audit automated tests for high-risk areas by analyzing changed symbols and implementation logic to identify data integrity, security, rollback, and compatibility risks. This surfaces a structured assessment prescribing concrete evidence needs and risk tiers for these critical areas.

A test suite audit works for pull requests and feature modules by mapping guarantees across unit, integration, and contract tests. It analyzes public entry points and changed symbols within the targeted scope to surface risk-aware ship readiness signals.

Do not rely solely on test coverage metrics when determinism shortfalls and weak oracles exist. Coverage percentage does not guarantee boundary fidelity or strong validation; a risk assessment audit is needed to map actual guarantees and prescribe concrete evidence requirements.