Customers Use Production,
Test Production!
Protect all golden-threads with DoesQCustomers Use Production,
Test Production!
Protect all golden-threads with DoesQCustomers Use Production,
Test Production!
Protect all golden-threads with DoesQCustomers Use Production,
Test Production!
Protect all golden-threads with DoesQCustomers Use Production,
Test Production!
Protect all golden-threads with DoesQCustomers Use Production,
Test Production!
Protect all golden-threads with DoesQA
The cookie banner sits over the button on every fresh test run. Set the consent cookie up front, then test Reject all: check the analytics cookie has no value.
https://t.co/eDV3u1A5Tz #QA#privacy
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.
https://t.co/eDV3u1A5Tz #QA#webtesting
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.
https://t.co/eDV3u1A5Tz #QA#Localisation
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.
https://t.co/eDV3u1A5Tz #MobileTesting#QA
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.
https://t.co/eDV3u1A5Tz #testautomation#QA
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.
https://t.co/eDV3u1A5Tz #testautomation#QA
Links break quietly when pages move. One Check links step requests every link on the page, and the Run names the one that failed.
https://t.co/kfSOmJLtuh #QA#WebDev
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.
https://t.co/k9xuAHHkiX #a11y#QA
A voucher button that does nothing throws no error, so the dashboard stays green. Monitoring watches your systems. Tests check your journeys. Use both.
https://t.co/eDV3u1A5Tz #Monitoring#QA#DevOps
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.
https://t.co/x7QwnqV8kM #QA#DevOps
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.
https://t.co/MKR1cmHf8X #TestAutomation#QA
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.
https://t.co/vXboqVL9g8 #FrightPath
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.
https://t.co/eDV3u1A5Tz #FrightPath
A failed Run only helps if someone sees it. Send passed and failed Runs to email, a webhook, Slack or Teams, and let the failure come to you.
https://t.co/2j6p9GeAsv #TestAutomation#QA
Fright Path, Night 18: My Agent Is a Friendly Ghost.
New commits overnight, and nobody at the keyboard: it's your coding agent. Connect it to DoesQA over MCP or the CLI, and it runs real journeys in real browsers, fixes what broke and hands you the Run as proof.
https://t.co/vXboqVL9g8 #FrightPath