Automation tooling
Comparisons and deep dives on test automation tooling, from Playwright to journey-based QA with DoesQA.
The internet is loud about tools that break. DoesQA is quiet because it works. That has cost us attention, not customers.
The internet is loud about tools that break. DoesQA is quiet because it works. That has cost us attention, not customers.
The internet is loud about tools that break. DoesQA is quiet because it works. That has cost us attention, not customers.
The internet is loud about tools that break. DoesQA is quiet because it works. That has cost us attention, not customers.
Same Start. Same End. Wildly Different Effort. One auth Flow with register and forgotten-password branches, side by side with a fair Playwright sketch.
Same Start. Same End. Wildly Different Effort. One auth Flow with register and forgotten-password branches, side by side with a fair Playwright sketch.
Same Start. Same End. Wildly Different Effort. One auth Flow with register and forgotten-password branches, side by side with a fair Playwright sketch.
Same Start. Same End. Wildly Different Effort. One auth Flow with register and forgotten-password branches, side by side with a fair Playwright sketch.
Free test automation frameworks like Playwright seem costless at first, but the real expense appears as teams scale. Running tests, managing infrastructure, and maintaining the system quickly add up. The framework is just the starting point, the true cost comes from everything around it.
Free test automation frameworks like Playwright seem costless at first, but the real expense appears as teams scale. Running tests, managing infrastructure, and maintaining the system quickly add up. The framework is just the starting point, the true cost comes from everything around it.
Free test automation frameworks like Playwright seem costless at first, but the real expense appears as teams scale. Running tests, managing infrastructure, and maintaining the system quickly add up. The framework is just the starting point, the true cost comes from everything around it.
Free test automation frameworks like Playwright seem costless at first, but the real expense appears as teams scale. Running tests, managing infrastructure, and maintaining the system quickly add up. The framework is just the starting point, the true cost comes from everything around it.
Set yourself up for success by splitting out your setup, functionality, and teardown within your test automation.
Set yourself up for success by splitting out your setup, functionality, and teardown within your test automation.
Set yourself up for success by splitting out your setup, functionality, and teardown within your test automation.
Set yourself up for success by splitting out your setup, functionality, and teardown within your test automation.
I see a variant of this question asked weekly in the r/QualityAssurance subreddit and figured it would be helpful if I summarised the pros and cons I've read for each test framework.
I see a variant of this question asked weekly in the r/QualityAssurance subreddit and figured it would be helpful if I summarised the pros and cons I've read for each test framework.
I see a variant of this question asked weekly in the r/QualityAssurance subreddit and figured it would be helpful if I summarised the pros and cons I've read for each test framework.
I see a variant of this question asked weekly in the r/QualityAssurance subreddit and figured it would be helpful if I summarised the pros and cons I've read for each test framework.
Software development teams can be divided into two camps: those who build Dark Mode early and those who choose to wait.
Software development teams can be divided into two camps: those who build Dark Mode early and those who choose to wait.
Software development teams can be divided into two camps: those who build Dark Mode early and those who choose to wait.
Software development teams can be divided into two camps: those who build Dark Mode early and those who choose to wait.
Get your next release tested end to end.
Hosted journeys with email, MFA, and branching. Shared Elements keep maintenance low. Pass and fail from real hosted browsers.
Get your next release tested end to end.
Hosted journeys with email, MFA, and branching. Shared Elements keep maintenance low. Pass and fail from real hosted browsers.
Get your next release tested end to end.
Hosted journeys with email, MFA, and branching. Shared Elements keep maintenance low. Pass and fail from real hosted browsers.