Dokimore Support Team
Walkthroughs and fixes written from the questions customers and evaluators ask.
- Articles
- 10
- Topics
- 2
- Last updated
What this team covers
Articles signed by this team
- Use CasesScenario walkthrough
Use Case: QA When Coding Agents Open the Pull Requests
A scenario walkthrough, not a customer story: a fourteen-engineer product team where coding agents open two pull requests in five. What the 2026 studies of agent-written tests measured, why the error path is the part nobody tests, and the four changes to a QA plan that keep the release gate independent of the code it judges.
- Use CasesScenario walkthrough
Use Case: Six Weeks Before Peak Season, What an Online Store Tests
A scenario walkthrough, not a customer story: a mid-sized store with one checkout, two payment providers and a promo banner that changes weekly plans its last six weeks before peak season. The 2025 numbers that set the stakes, a week-by-week test plan, and the honest limits of running load from one region within a plan’s virtual-user cap.
- Use CasesScenario walkthrough
Use Case: Testing an AI Assistant Before Release: Injection, Leaks, Cost and a Regression Eval
A scenario walkthrough, not a customer story: a product team adds a support assistant on a third-party model and has three weeks to a release. The four checks that stand between the demo and production, the OWASP list they map to, the EU AI Act dates that apply from August 2026 and the ones that moved, and how a gateway with detectors, a budget gate and a regression eval turns each check into evidence.
- Use CasesScenario walkthrough
Use Case: Release Verification, One Flow Checked Before the Deploy and Monitored After It
A scenario walkthrough, not a customer story: a team whose end-to-end suite is green on every deploy and whose customers still find the failures first. The case, made at SREcon by an Elastic engineer, that synthetic monitoring and end-to-end testing are two sides of one coin; the production-only failure no staging run can see; and how one flow is checked before the deploy by its recording and watched after it by the API collection behind it, with what runs where.
- Best PracticesHow-to guide
How to Fix Flaky Tests: Find the Cause Before You Retry
A flaky test passes and fails on the same code, and every retry that turns it green teaches a team to ignore red builds. This guide puts numbers on the causes from the studies that measured them, shows how to find flaky tests before they spread, fixes each cause at its root, and covers what Playwright, Cypress and Selenium ship for the job.
- Use CasesScenario walkthrough
Use Case: Smart Test Selection in CI, or Why Your 45-Minute Pipeline Is a Choice
A scenario walkthrough, not a customer story: a team runs 2,400 tests on every commit and waits 45 minutes for a signal. Test selection maps the change to the tests it can reach and runs those, with a written reason per pick and a confidence score that says when to run everything. What the published research measured, what Playwright ships for free, and what Dokimore adds.
- Best PracticesExplainer
WCAG 2.2 Changed the Rules. Here Is What a Product Team Has to Do
WCAG 2.2 became a W3C Recommendation on 5 October 2023 with nine new success criteria, most of them about focus, pointer targets, repeated entry and sign-in. Which ones apply to a typical web application, what an automated audit can and cannot decide, how the European rules reference it, and how a VPAT is drafted from a scan.
- Use CasesScenario walkthrough
Use Case: Moving 1,200 Selenium Tests Without a Big-Bang Rewrite
A scenario walkthrough: a team with 1,200 Selenium tests records the flows those tests protect, runs the recorded suite beside the old one with fallback locators underneath, retires each Selenium test once its recorded equivalent has passed for a release or two, and keeps the exit open by exporting the result as Playwright, Selenium, Robot Framework or pytest code. There is no importer, and this article says what Selenium still does better.
- Best PracticesExplainer
Test Automation That Outlasts Its Champion: When They Quit, What Survives?
Automation initiatives die when the one engineer who owned them leaves. The patterns that survive turnover are boring and written down: an owner and a ticket for every flaky test, one shared element repository, repairs that are visible in the run, a named set of must-pass flows, and schedules that do not depend on memory. Three companies have published what happened when they put a recorded owner on flaky tests; Spotify’s number is here.
- Best PracticesExplainer
GDPR-Safe Test Data: Production Data in Staging Is an Incident Waiting to Happen
Restoring a production dump into staging is one of the most common test-data strategies, and under the GDPR every obligation follows the copy into an environment with weaker access control, more debug logging and more third-party tooling. Synthetic generation from rules produces realistic records that belong to nobody, which takes those datasets out of the regulation’s scope; masking is for the cases that genuinely need production-shaped data, and the masked copy is still personal data. Dokimore does both. What the law says, what the product does, and what it does not promise.
What its articles carry
- 10 of 10 list their outside sources, each with the date it was read.
- 10 of 10 say how their numbers were measured, under “How we measured this”.
- 10 of 10 answer the questions readers ask, one paragraph each.
- An article that changes after publication shows the date it was updated.