QA Review

Review quality strategy the way a strong QA engineer would: choose the right test layers, verify the tests are readable and deterministic, and make failures easy to act on.

When to Use

• A feature or PR needs a QA-oriented review before merge or release
• Test coverage exists, but you are not sure it is at the right pyramid level
• A team needs a repeatable checklist for API, UI, regression, or performance coverage
• Bug reports or CI failures are noisy and need better quality standards

When NOT to Use