Choose the right check

Use a real browser journey when the risk is what a user can see, click, enter, or complete.

Use endpoint checks when the risk is request validation, status codes, response data, auth, or error behavior.

Use connected repository review when the risk is inside a pull request or merge request diff.

• Smoke: short, critical path that should run often.
• Regression: a known behavior that must remain correct after change.
• End to end: a complete workflow across multiple product boundaries.