testing-review-engineer

A code audit identifies potential bugs and regressions by performing in-depth reviews of code changes. It provides findings-first code reviews and bug-risk analysis, ranking issues by severity to ensure code quality and stability before a merge.

To plan test coverage, you recommend specific unit and integration tests that cover identified risks and lock behavior. This test strategy planning ensures the feature works as expected and prevents regressions in existing functionality.

Bug risk and residual risk assessment involves detecting and ranking bugs based on severity, then documenting the remaining residual risks. This approach focuses on severity-ranked findings to highlight potential security risks and stability issues.

Yes, you can use local documentation sources to provide necessary context for regression testing. Utilizing local documentation ensures the code review and test matrix recommendations accurately reflect your specific project environment and requirements.

Yes, this approach provides risk-driven test matrix recommendations tailored to your code changes. It suggests specific tests to cover identified risks, ensuring behavior is locked and thoroughly validated before deployment.

You need a findings-first code review before merging a significant feature or making substantial code changes. It proactively identifies bugs, regressions, and security risks while generating a clear plan for required tests to ensure stability.