When the purchase event stops firing, the site still works and the reports quietly go wrong. Check GTM event confirms it fired, with the right transaction ID.
does.qa #Analytics #QA
34
Card fields in an iframe, terms in a new tab. Switch frame steps into the card form and back out; Switch window finds the new tab. All in one Flow.
does.qa #QA #Ecommerce
49
Staging behind a password? Tick Basic Auth in the Open step and take the username and password from Values. Custom Headers mark your test traffic.
does.qa #QA #webtesting
42
Your customers aren't all on office wifi in your timezone. The Open step can set a Throttle, a Language and a Timezone, so you see the date a shopper in Tokyo sees.
does.qa #QA #Localisation
35
Looks fine on your screen, falls apart on a phone. The Open step has a Simulated Device Runner with 46 Variants, so one Flow runs on phones and tablets as separate Test Cases.
does.qa #MobileTesting #QA
37
The demo journey always works. Customers mistype passwords, empty baskets, use expired cards and press back. One Flow, many Test Cases: test the unhappy paths too.
does.qa #testautomation #QA
35
Your test suite is a product. It has users, an owner, maintenance, and tests that should be retired. When nobody owns it, it goes red and the team stops looking.
does.qa #testautomation #QA
40
Every kind of testing serves one goal: confidence. Every line of custom test code is something you own.
does.qa/blog/code-has-everyt… #TestAutomation #QA
27
Links break quietly when pages move. One Check links step requests every link on the page, and the Run names the one that failed.
docs.does.qa/better-coverage… #QA #WebDev
36
Six key parts of an automated regression pack, from critical flows to a test for every bug you fix.
does.qa/blog/6-key-parts-of-… #RegressionTesting #QA
33
If someone can't use your checkout with a keyboard or a screen reader, it isn't working. Add accessibility checks to the journeys you already test.
docs.does.qa/better-coverage… #a11y #QA
43
A voucher button that does nothing throws no error, so the dashboard stays green. Monitoring watches your systems. Tests check your journeys. Use both.
does.qa #Monitoring #QA #DevOps
31
Copies of a Flow per environment drift. Keep one Flow, store the base URL and logins as Values, and let a Run Recipe swap them for staging or production.
docs.does.qa/better-coverage… #QA #DevOps
43
Flaky isn't a category. It's a failure nobody has investigated yet. Stop on red.
does.qa/blog/stop-on-red-why… #FlakyTests #QA
38
Two-factor codes keep accounts safe, and stop a lot of login tests. Save the secret once, add a Set MFA step, and every Run signs in like your users do.
docs.does.qa/configuration/m… #TestAutomation #QA
45
Every test passed. Customers couldn't see the button. Check how the page looks, not just what's in the code.
does.qa/blog/visual-regressi… #VisualTesting #QA
1
54
Fright Path, Night 20: The Final Run.
Halloween night: every monster is out, and so is the team. Scheduled Runs keep watch hour after hour, the alert lands in Slack with the AI Summary following in its thread, and the next Run has already started.
does.qa #FrightPath
1
64
Trick or Tested.
Our logo dressed up for Halloween. Your tests don't have to be scary.
does.qa
#FrightPath
45
Fright Path, Night 19: I See Dead Tests.
Skipped, commented out, checking that true is true, and the report stays green. In DoesQA, a Flow that checks nothing is labelled No checks, and Pack Health scores your test pack out of ten.
does.qa #FrightPath
34