Article archive
Do not start by telling the testers to go faster. First work out what they are spending the time on. Slow testing is often a symptom. Broken environments, poor test data, late builds, enormous regression packs, duplicated approval steps, flaky automation and…
It is a testing problem in the sense that testing cannot happen properly. It is not automatically the test team’s fault. A broken environment can destroy more testing time than any poorly written test case. Builds fail. Data vanishes. Services point to…
Probably more than you did while building it, but nowhere near as much as a bank needs. The useful answer depends on what the app can damage when it gets things wrong. If this is a small side project, you can absolutely…
A good test report should help somebody make a decision. If it mainly proves the test team has been busy, it is an activity report wearing a tie. Management does not need every test case. It needs the truth about risk. A…
If testing is miles behind a month before launch, the answer is not to invent a heroic recovery plan showing how every missed activity will somehow fit into the remaining time. You have already lost the time. The…
This happens because people confuse two different things: testing provides evidence; management makes the release decision. Testers do not own the launch date, and managers do not get to rewrite test results because…
No. Releasing with known defects is not automatically bad testing, bad management or the beginning of the apocalypse. Almost every serious product ships with known defects at some point.
The fastest way to get the wrong answer after a failed release is to ask “why didn’t testing catch this?” before you have even established what happened.
If every release needs a bridge call, fifteen people staring at dashboards and someone saying “can everybody mute unless speaking”, you do not have a heroic support process. You have normalised unstable releases.
Finding serious defects late does not necessarily mean your testers are doing a bad job. It may mean they are finally being given a complete enough system to find them.