Loading…
The test pyramid, TDD, mocks vs fakes, flaky tests and what to test at each layer.
Your new team says "CI runs the tests on every push and every pull request." What is continuous integration, and why is it worth running the tests automatically on every change instead of before each release?
Your pull request has approval, but one test is failing in CI. It is in a part of the code you did not touch, and the deadline is today. What should you do, and what should you not do?
You are setting up a CI pipeline for a web service. It needs to run a linter, compile the code, run unit tests, run integration tests that need a database, and build a container image. In what order would you put these steps, and why?
A test passes on your laptop but fails in CI with "module not found". Your teammate shrugs: "works on my machine." What kinds of differences between a laptop and a CI machine cause this, and how does a team reduce them?
The full test suite takes 25 minutes in CI. Before pushing a change, what would you run on your own machine, and what can you leave to CI?
Your pull request's CI job is red and the log is 4,000 lines long. Walk through how you would find out what actually failed.