Note for buyers
Questions to ask a vendor about a migration case before you rely on it
Research desk, testautomationvendors.com · published 2026-11-12 · data as of 2026-11-12 · 11 records
- 11
- migration cases
- 8
- omit duration
- 7
- state no before value
11 verified cases describe a framework migration. 5 state the suite size, 3 the duration and 4 a before value for any metric.
What stands out
- 01Testrig Technologies publishes 3 of the 11 migration cases; the three vendors with the most publish 7, so a reader is looking at a concentrated set of sources.
- 0211 of 29 metrics in these cases state a before value; across all 639 metrics in the dataset the count is 209.
- 032 of 11 reach grade A, which needs a named client and one metric with both a before value and a stated method.
- 04The field left out most often is start year: 9 of 11 cases do not state it.
Counts come from verified records. A baseline is the before value a vendor states for a metric; quoted claims carry their grade and baseline flag.
- baseline:
- The measured value before the work started, against which a later value is compared. source
Questions derived from the gaps
How many tests moved, and how many were rewritten rather than converted: 6 of 11 cases do not say.
How long the migration took and with how many people: 8 of 11 cases omit duration and 8 omit team size.
What the run time and failure rate were before and after: 7 of 11 cases state no before value.
The cases
a1qa-10: a1qa, Spectron to Playwright, anonymous client, grade C.
deviqa-2: DeviQA, Cypress to Playwright, Agorapulse, grade A.
deviqa-4: DeviQA, Selenium WebDriver to Cypress, Renhead, grade B.
qa-wolf-2: QA Wolf, Cypress to Playwright, Xima, grade B.
qawerk-8: QAwerk, Mocha to Cypress, Union54, grade B.
qualitylogic-1: QualityLogic, Protractor to Playwright, anonymous client, grade C.
testrig-1: Testrig Technologies, Cypress to Playwright, anonymous client, grade C.
testrig-3: Testrig Technologies, Selenium WebDriver to Playwright, anonymous client, grade C.
testrig-6: Testrig Technologies, Ghost Inspector to Cypress, anonymous client, grade C.
thinksys-1: ThinkSys, WebdriverIO to Playwright, Boostlingo, grade A.
thinksys-3: ThinkSys, Selenium WebDriver to Playwright, CRIO (Clinical Research IO), grade B.
Questions
How many migration cases name the client?
6 of 11.
Does the site compare source and target frameworks?
No. It records what the cases disclose.
Which flows have pages?
Flows with 3 or more cases.
What is the most useful single figure to ask for?
The suite size before and after, with the run time for both on the same hardware.
Records used
This post reads 11 records; the newest verifiedOn date among them sets the data-as-of date.
Show record ids
a1qa-10, deviqa-2, deviqa-4, qa-wolf-2, qawerk-8, qualitylogic-1, testrig-1, testrig-3, testrig-6, thinksys-1, thinksys-3
More from the blog
Note for buyers
How to read a test automation case study: the fields that are usually missing
222 of 263cases omit start year
Field by field, how often 263 verified automation cases leave out team size, duration, baseline, client name and CI.
data as of 2026-11-12 · 263 records
Note for buyers
Why a percentage without a baseline is a claim, not a result
246percentage claims
246 percentage claims in verified automation cases, and how many state the starting value.
data as of 2026-11-12 · 126 records
Note for buyers
What an automation coverage figure can mean: the denominators seen in published cases
88coverage claims
88 coverage claims sorted by what they measure: test cases, regression effort, features or code.
data as of 2026-11-12 · 76 records
Related pages
Scores and grades describe published evidence as of the verifiedOn date on each item. They do not measure service quality. Verify with the vendor before contracting.