Skip to main content
This guide takes you from a feature with thin tests to tests that run on every build. You review every test before it is merged.
1

Find the gaps and generate tests

Pick an existing feature, find where coverage is thin and generate tests that follow your project’s conventions. See Generate tests for existing code.
2

Review the generated tests

Inspect the changed files before you accept them, using the diff summary and verification checklist. See Review code changes.
3

Run the tests in your pipeline

Add a Test Suite stage so unit and integration tests run automatically, with the triggers and run policies you choose. See Test Suite pipeline stage. Add a Code Quality stage for linting and static analysis.
4

Gate every build

Run code review, code quality and test checks before every build so gaps are caught before release. See Configure pre-build workflows.
5

Keep it going as code changes

Ask for an independent review of a branch or pull request at any time. See Standalone Code Review Agent.

You are done when

  • New tests are merged and pass in your pipeline.
  • A failing test blocks the build before release.

Next

Ship from first commit to production

Modernize a legacy codebase