Stage 4 · Lesson 3 of 8
Testing your change and passing CI
Every change should come with evidence that it works. That means new or updated , a local run of the relevant tests, and passing (CI) checks before you ask for review. CI is a service that builds and tests every change automatically.
Copy the patterns in nearby tests rather than inventing your own. For a bug, write a test that fails before your fix and passes after it. For visual changes, add screenshots.
If CI fails for a reason you do not understand, read the log carefully and ask. Do not just re-run it until it turns green. Tests also protect your change from being broken later.
Common trapdeleting or skipping a failing test to get green, which hides a real problem and loses reviewers' trust fast.
A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it
Resources for this stage
Start with· follow one of these
- GuideFreeGoogle Engineering Practices
Google · Intermediate
Google's guides for change authors and reviewers: small changes, good descriptions and handling comments
- BookPaidThe Missing README: A Guide for the New Software Engineer
Chris Riccomini and Dmitriy Ryaboy (No Starch Press) · Beginner · $29.99 print, $23.99 ebook
The testing, code review, delivery and on-call chapters written for a new engineer