Running Tests
Our current CI doesn't do anything interesting.
Just like my ex.
A good CI pipeline typically includes:
- Unit tests
- Integration tests
- Styling checks
- Linting checks
- Security checks
- Any other kind of automated test
If any of the tests fail, the build is considered "broken" and the developer is notified (in our case by GitHub) so they can fix it.
Assignment
The Notely repo has, gasp, zero unit tests!
- Add a couple unit tests for the
GetAPIKeyfunction in theinternal/auth/auth.gofile.
If you're still a little fuzzy on how to write unit tests in Go, I'd highly recommend Dave Cheney's excellent blog post on the subject.
- Run them locally to make sure they work:
go test ./...
The ./... tells Go to run all tests in the current directory and all subdirectories.
Run and submit the CLI tests from the root of your repo.
The Boot.dev CLI requires you to be signed in to submit your solution!
Copy/paste one of the following commands into your terminal:
Run
bootdev run 3180c16a-cd04-4cbd-adee-ddb4d1b1ba34
Submit
bootdev run 3180c16a-cd04-4cbd-adee-ddb4d1b1ba34 -s
Run the CLI commands to test your solution.
- go test ./...
- Expecting exit code: 0
Using the Bootdev CLI
The Bootdev CLI is the only way to submit your solution for this type of lesson. We need to be able to run commands in your environment to verify your solution.
You can install it here. It's a Go program hosted on GitHub, so you'll need Go installed as well. Instructions are on the GitHub page.