Getting your first test merged
From a dashed violet line to a solid one. Most of the time is spent waiting on GitHub.
Pick a line, press + Test, approve the pull request. Nothing reaches your repository until you merge it yourself.
Before you start
You need an app connected and its map drawn. If the map is empty, guide 2 comes first.
The five steps
- 1Pick a dashed violet lineDashed violet means nothing tests it yet. A line from a page to the route it calls is a good first one.
- 2Press + TestThe panel says what the test would show, and what it wouldn’t. Read the second half too.
- 3Press Write it for meWe write one test file on our own branch and open a pull request in your app. The line turns teal and dashed, with Writing on it, then In review.shipready/test-checkout-billing
- 4Merge it on GitHubNothing merges without you. If your app runs its own checks on pull requests, they run first.
- 5Watch the lineOnce the test has run on your main branch and passed, the line goes solid. The letters on both boxes stay where they were.
What doesn’t change
The grade on either box. Writing a test won’t change a grade. A test proves what your code already does; it doesn’t change your code.
Next guide · 5 of 5