Skip to content
Test Automation Vendors / 263 cases

Cross-case count

What migrations vendors publish: from and to, counted

Research desk, testautomationvendors.com · published 2026-11-12 · data as of 2026-11-12 · 11 records

11
migration cases
8
flows
6
with before and after

11 verified cases are tagged as migrations across 8 flows. 6 state a before and an after value for at least one metric.

What stands out

  1. 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.
  2. 0211 of 29 metrics in these cases state a before value; across all 639 metrics in the dataset the count is 209.
  3. 032 of 11 reach grade A, which needs a named client and one metric with both a before value and a stated method.
  4. 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

Flows

A flow gets its own page at 3 or more cases.

FromToCasesPage
CypressPlaywright3/migrations/cypress-to-playwright/
Selenium WebDriverPlaywright2below threshold
Ghost InspectorCypress1below threshold
MochaCypress1below threshold
ProtractorPlaywright1below threshold
Selenium WebDriverCypress1below threshold
SpectronPlaywright1below threshold
WebdriverIOPlaywright1below threshold

The evidence ladder

Each row counts the migration cases that make that disclosure; the rows are separate counts, ordered from the most basic disclosure to grade A. Of 11 migration cases, 2 reach grade A, and the rarest disclosure below it is "state baseline and method for one metric" (2 cases).

The right-hand column gives the same steps for all 263 verified cases, so a reader can set this subset against the whole dataset.

The evidence ladder
Table view
ItemCount
Name a listed framework11
Name the client6
Publish at least one metric8
State a baseline for a metric4
State baseline and method for one metric2
Reach grade A2
Total33
StepMigration casesAll verified cases
Name a listed framework11 of 11263 of 263
Name the client6 of 1191 of 263
Publish at least one metric8 of 11210 of 263
State a baseline for a metric4 of 1175 of 263
State baseline and method for one metric2 of 1135 of 263
Reach grade A2 of 1118 of 263

What the migration cases disclose

Team size: 3 of 11. Duration: 3 of 11. Suite size metric: 5 of 11.

Questions

What counts as a migration case?

A case that describes moving an existing suite from one framework or tool to another.

Does this compare the frameworks involved?

No. It counts published cases per flow.

How many migration cases have before and after values?

6 of 11.

Which flows have pages?

Flows with 3 or more cases.

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

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.