Fright Path, Night 16: The Button Nobody Could Hear.
To a screen reader, the basket says button, button, button, and every test still passes. With DoesQA, accessibility checks are steps in your Flows, and a button with no accessible name fails the test.
does.qa #FrightPath
Every test was green. The AI was rewriting the tests so they'd pass. Re-run with the original selectors, the pass rate was 14%.
The green tick is a signal, not a verdict.
does.qa/blog/every-test-was-… #QA
Fright Path, Night 15: The Order That Never Existed.
The thank-you page showed an order number, but nothing was saved or charged, and the test passed because it stopped there. Store the order number, call your own API with it, and check what was really saved.
does.qa #FrightPath
Run your test pack filtered by tags, override Values for just that Run, then save it as a Run Recipe so it's one click away next time. Run History keeps every Run.
docs.does.qa/runs/start-a-ru… #TestAutomation #QA
Playwright is free to start. Then 20 runners become 200, and you're maintaining runners, CI, reporting and debugging. The real cost is everything you build on top.
does.qa/blog/the-real-cost-o… #Playwright #QA
Fright Path, Night 14: The Hour That Happened Twice.
Last night UK clocks went back, and half past one happened twice: two customers, one table. One Flow, three Open steps on London, New York and Sydney time, and the midnight bug shows up in a working-day Run.
does.qa #FrightPath
Fright Path, Night 13: The Vampire Has No Reflection.
The Add to basket button passes every check, but a style change made it white on white. Vision steps check how the page actually looks: against a control image, or what a person should see, in plain English.
does.qa #FrightPath
Fright Path, Night 12: The Doppelgänger.
A feature flag sends some customers to a new checkout your tests never saw. Set the cookie or local storage value your flag reads, branch for both twins, and the new checkout fails at Pay now.
does.qa #FrightPath
Four test smells: the just-rerun-it test, DOM archaeology, the mock museum, and the green build nobody believes. Good tests fade into the background.
does.qa/blog/i-can-smell-you… #QA #FlakyTests
Your app can break on a day nobody deployed. Scheduled Runs keep checking: pick what to run, drag across the hours, and hear about failures in Slack, Teams, email or a webhook.
docs.does.qa/configuration/s… #TestAutomation #QA
Fright Path, Night 11: Skeletons in the Loading Screen.
Fine on office Wi-Fi, skeletons forever on a train. Throttle the network to 3G, 2G or offline, check the load time, wait for real results, and run each connection as its own Test Case.
does.qa #FrightPath
Same test, two tools. Register with email verification or reset a password: in DoesQA it's one Flow and two Test Cases; in Playwright, page objects, a mail helper and two specs.
does.qa/blog/doesqa-vs-playw…
Test sign-up emails and password resets with no inbox to set up. Every Test Case gets its own inbox: wait for the email, open it, touch the link. Email steps are on Pro.
does.qa #QA #TestAutomation
Fright Path, Night 10: The Haunting of Staging.
It passed yesterday. Today the test user already exists and the voucher's been used. With built-in Values, every Test Case signs up a new customer, so tests run side by side without haunting each other.
does.qa #FrightPath
Fright Path, Night 9: The Shapeshifter.
The login code keeps changing, so the login test got skipped. Save the test user's MFA secret once, and a Set MFA step fills in the current code on every Run. Two-factor stays on, and the real login gets tested.
does.qa #FrightPath
Your first DoesQA test: create a Flow, type the steps as sentences, press Run.
The guide: docs.does.qa/getting-started…
Connect DoesQA to Claude: add mcp.ai.does.qa/mcp as a connector, click Connect, approve the token in DoesQA. Nothing to copy or paste.
Then ask what your test pack covers: does.qa
Fright Path, Night 8: The Cursed Spreadsheet.
Hundreds of rows, all by hand, and row 212 says “pass (I think)”. Rows become Flows, a Run Recipe runs the lot before every release, and every Run lands in Run History with screenshots as proof.
does.qa #FrightPath