review-community-standard-componentization-tests-knowledge

Reviewing TDD test quality involves comparing RED tests against the code diff to identify coverage gaps, then assessing test pyramid balance, AAA formatting, and fixture quality to ensure alignment with planned changes.

Checking edge-case coverage and fixture quality involves evaluating Given-When-Then patterns and mock discipline, using plan-aware evaluation against code diffs to identify missing edge cases and opportunities to improve fixture reliability.

Assessing test pyramid balance involves evaluating the distribution of unit, integration, and end-to-end tests within the plan, comparing RED tests against code diffs and applying canonical best practices sourced via web research to guide decisions.

Web search is needed to validate current TDD and BDD best practices during a review, sourcing canonical guidance via web research during evaluation to reduce ambiguity and ensure decisions align with up-to-date industry standards.

AAA formatting matters when reviewing tests for componentization because it enforces clear Arrange-Act-Assert separation, and evaluating AAA alongside Given-When-Then patterns ensures test readability and adherence to structured BDD practices.