Case studies
Other people’s migrations, read properly.
We have no client case studies to show you, so we will not invent any. Instead we take the best publicly documented accounts in this field and read them closely, including the parts that argue against hiring anyone at all. Every number below traces to a published source you can check.
What a real Selenium migration timeline looks like
One hundred tests, eight months, two sets of tests running side by side. The number vendors never lead with.
Read the case studyTwo weeks, 200 tests, and the part everyone skips
A fortnight for 200 tests, GPT-4 inventing checks that do not exist, and why 71% passing on a laptop became 44% on the build server.
Read the case studyThe automation project that found eight bugs in three years
A quality director published her own three-year failure. Going back to manual testing may have been right.
Read the case studyZalando load tests in production. Here is why.
At 7,200 orders a minute, a test copy of the site stops telling you anything worth knowing.
Read the case studyNobody is coming to test it for you
Amazon went from ten engineers per tester to a hundred. The testing work did not go anywhere.
Read the case study