Extras · 1 of 4

A typical day

Check what broke overnight in the automated test run and work out whether it is a real failure or a flaky test. Pick up the new features and try to break them: odd inputs, bad network, the wrong order, the thing nobody planned for. Write up what you find precisely enough that a developer can reproduce it without asking you. Then meetings about whether the release is ready, where you are usually the one saying not yet.