Skip to content
Test Automation Vendors / 263 cases

Framework note

Cypress: what the published cases show

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

25
verified cases
10
vendors
11 of 25
name the client
40 of 59
metrics with a baseline

25 verified cases in this dataset name Cypress, published by 10 vendors. Grades: A 4, B 9, C 12. 11 of 25 name the client, and 40 of 59 published metrics state a baseline.

What stands out

  1. 01DeviQA publishes 8 of the 25 Cypress cases; the three vendors with the most publish 16, so a reader is looking at a concentrated set of sources.
  2. 0240 of 59 metrics in these cases state a before value; across all 639 metrics in the dataset the count is 209.
  3. 034 of 25 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 duration: 20 of 25 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

01Cases, vendors and grades

The count covers every verified case whose text names Cypress, including vendors outside the ranked 12.

Vendors with cases: a1qa (1), Codoid (5), DeviQA (8), QA Madness (1), QA Wolf (1), QAwerk (1), TestDevLab (1), TestFort (2), TestingXperts (2) and Testrig Technologies (3).

Cases, vendors and grades
Table view
ItemCount
Grade A4
Grade B9
Grade C12
Total25

02Clients and industries

Named clients appear in 11 cases; 14 keep the client anonymous.

Industries stated: Childcare management software (1), Cloud customer support software (1), Contact center software (1), Corporate learning (LearnOps) software (1), Drone inspection software (1), E-Commerce (1), E-commerce fulfillment and warehouse management (1) and EdTech (English learning) (1).

Client types stated: startup (2) and enterprise (1).

03Metric kinds and baselines

The Cypress cases publish 59 metrics. 40 state a baseline and 4 state both a baseline and a method.

  • “Regression cycle reduced from 4 days to 3 hours.”before 4 days after 3 hours Codoid codoid-1 grade B, partial baseline yes method no
  • “4,000+ automated UI and API tests created”before No UI or API test automation after 4,000+ automated UI and API tests DeviQA deviqa-3 grade A, verified baseline baseline yes method no
  • “1,000+ automated API tests created”before API testing was performed manually after 1,000+ automated API tests DeviQA deviqa-3 grade A, verified baseline baseline yes method no
  • “smoke tests run every 2 hours across two frameworks and complete in 15–20 minutes”before No automated smoke testing after 15–20 minutes DeviQA deviqa-3 grade A, verified baseline baseline yes method no
  • “targeted API suite runs after each pull request and completes in approximately 10 minutes”before No tests ran automatically after developers submitted pull requests after approximately 10 minutes DeviQA deviqa-3 grade A, verified baseline baseline yes method yes
  • “Test suites cover the three latest Chrome versions and two Safari versions”before No automated coverage across browser versions after three latest Chrome versions and two Safari versions DeviQA deviqa-3 grade A, verified baseline baseline yes method no
Metric kindMetricsWith baseline
other169
execution-time1513
suite-size1411
coverage86
cost20
defects20
release-frequency21

04Languages, CI tools and clouds named alongside

Languages: JavaScript (8), TypeScript (6), Ruby (2), Java (1) and Python (1).

CI tools: GitHub Actions (6), Jenkins (6), GitLab (3), Azure DevOps (2), CircleCI (2), AWS CodeCommit (1), Bitbucket Pipelines (1) and Bitrise (1).

Device or browser clouds: BrowserStack (6), LambdaTest (3) and AWS (2).

05Migration flows

3 cases move a suite to Cypress and 3 cases move a suite away from it.

Flows: Cypress to Playwright (3), Ghost Inspector to Cypress (1), Mocha to Cypress (1) and Selenium WebDriver to Cypress (1).

06The evidence ladder

Each row counts the Cypress cases that make that disclosure; the rows are separate counts, ordered from the most basic disclosure to grade A. Of 25 Cypress cases, 4 reach grade A, and the rarest disclosure below it is "state baseline and method for one metric" (4 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 framework25
Name the client11
Publish at least one metric14
State a baseline for a metric9
State baseline and method for one metric4
Reach grade A4
Total67
StepCypress casesAll verified cases
Name a listed framework25 of 25263 of 263
Name the client11 of 2591 of 263
Publish at least one metric14 of 25210 of 263
State a baseline for a metric9 of 2575 of 263
State baseline and method for one metric4 of 2535 of 263
Reach grade A4 of 2518 of 263

07Frameworks named alongside Cypress

17 of 25 cases name at least one other listed framework. The pairing shows which stacks vendors describe together, not which combination works.

Frameworks named alongside Cypress
Table view
ItemCount
Postman and Newman9
Appium7
Apache JMeter4
Selenium WebDriver3
WebdriverIO3
Playwright2
Cucumber, SpecFlow, Behave1
Gatling1
Total30

08Where the cases come from

DeviQA (8), Codoid (5) and Testrig Technologies (3) publish the most Cypress cases. A vendor with many cases here shows breadth of published work; the grade columns show how much of it can be checked.

VendorCasesGrade A or BWith a baselined metric
DeviQA888
Codoid521
Testrig Technologies300
TestFort200
TestingXperts200
a1qa100
QA Madness100
QA Wolf110
QAwerk110
TestDevLab110

09What vendors leave out

12 of 25 cases do not state a team size and 20 do not state a duration.

2 of 59 metrics are cost figures and 0 mention flakiness, so maintenance cost and flaky test rates are rarely published.

10Questions for a Cypress proposal

Ask for suite size and run time before and after the work: 17 of 25 cases give no before value for either.

Ask for the flaky test rate over a stated number of runs: 0 of 59 metrics mention flakiness at all.

Ask who owns maintenance after hand-over and what it costs per month: 2 of 59 metrics are cost figures.

Ask for a reference client you can call: 14 of 25 cases keep the client anonymous.

Questions

How many vendors have published Cypress cases?

10 vendors in this dataset, with 25 verified cases between them, as of the dataAsOf date on this page.

How many Cypress cases name the client?

11 of 25. A named client is required for grade A.

Do Cypress case studies publish baselines?

40 of 59 metrics state a before value.

Does this page rank Cypress against other frameworks?

No. The site counts which vendors have evidence on a framework and never compares frameworks.

Records used

This post reads 25 records; the newest verifiedOn date among them sets the data-as-of date.

Show record ids

a1qa-32, codoid-1, codoid-8, codoid-13, codoid-33, codoid-34, deviqa-3, deviqa-4, deviqa-5, deviqa-6, deviqa-11, deviqa-18, deviqa-20, deviqa-42, qa-madness-1, qa-wolf-2, qawerk-8, testdevlab-3, testfort-1, testfort-21, testingxperts-1, testingxperts-2, testrig-6, testrig-8, testrig-10

More from the blog

Framework note

Playwright: what the published cases show

48verified cases

48 verified cases from 14 vendors name Playwright: grades, client types, metric kinds, stacks and the fields vendors leave out.

data as of 2026-11-12 · 48 records

Framework note

Selenium WebDriver: what the published cases show

88verified cases

88 verified cases from 13 vendors name Selenium WebDriver: grades, client types, metric kinds, stacks and the fields vendors leave out.

data as of 2026-11-12 · 88 records

Framework note

WebdriverIO: what the published cases show

16verified cases

16 verified cases from 6 vendors name WebdriverIO: grades, client types, metric kinds, stacks and the fields vendors leave out.

data as of 2026-11-12 · 16 records

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.