Framework note
WebdriverIO: what the published cases show
Research desk, testautomationvendors.com · published 2026-11-12 · data as of 2026-11-12 · 16 records
- 16
- verified cases
- 6
- vendors
- 10 of 16
- name the client
- 41 of 64
- metrics with a baseline
16 verified cases in this dataset name WebdriverIO, published by 6 vendors. Grades: A 2, B 11, C 3. 10 of 16 name the client, and 41 of 64 published metrics state a baseline.
What stands out
- 01DeviQA publishes 10 of the 16 WebdriverIO cases; the three vendors with the most publish 13, so a reader is looking at a concentrated set of sources.
- 0241 of 64 metrics in these cases state a before value; across all 639 metrics in the dataset the count is 209.
- 032 of 16 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 duration: 12 of 16 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 WebdriverIO, including vendors outside the ranked 12.
Vendors with cases: a1qa (2), Abstracta (1), Codoid (1), DeviQA (10), QAwerk (1) and Testrig Technologies (1).
Table view
| Item | Count |
|---|---|
| Grade A | 2 |
| Grade B | 11 |
| Grade C | 3 |
| Total | 16 |
02Clients and industries
Named clients appear in 10 cases; 6 keep the client anonymous.
Industries stated: Carbon management and ESG software (1), Childcare management software (1), Cryptocurrency wallet (1), Dental laboratory case management (1), E-Commerce (1), EdTech (English learning) (1), Fashion retail eCommerce (1) and Food & Beverage (1).
Client types stated: enterprise (1).
03Metric kinds and baselines
The WebdriverIO cases publish 64 metrics. 41 state a baseline and 6 state both a baseline and a method.
- “Cut combined mobile + web regression execution to ~35 minutes (from multi-day cycles)”before multi-day cycles after ~35 minutes Abstracta abstracta-2 grade B, partial baseline yes method no
- “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
- “700+ autotests were migrated to a new framework”before Outdated autotests for the Chrome extension after 700+ autotests DeviQA deviqa-8 grade B, partial baseline yes method no
- “70+ performance scripts were created using K6 and JMeter”before No performance tests after 70+ performance scripts DeviQA deviqa-8 grade B, partial baseline yes method no
- “Covered ~95% functionality with BE tests”before No back-end autotests after ~95% functionality DeviQA deviqa-8 grade B, partial baseline yes method no
- “15+ jobs were configured to monitor the critical features daily”before Critical features weren’t monitored after 15+ jobs DeviQA deviqa-8 grade B, partial baseline yes method no
| Metric kind | Metrics | With baseline |
|---|---|---|
| suite-size | 18 | 13 |
| execution-time | 16 | 9 |
| other | 13 | 9 |
| coverage | 12 | 8 |
| defects | 4 | 1 |
| release-frequency | 1 | 1 |
04Languages, CI tools and clouds named alongside
Languages: TypeScript (9), JavaScript (4), Java (3) and Ruby (1).
CI tools: CircleCI (4), GitHub Actions (3), Jenkins (3), Azure DevOps (1), Bamboo (1), Bitbucket CI (1), Bitbucket Pipelines (1) and Bitrise (1).
Device or browser clouds: BrowserStack (7), LambdaTest (2), Kobiton (1) and Sauce Labs (1).
05Migration flows
0 cases move a suite to WebdriverIO and 1 case moves a suite away from it.
Flows: WebdriverIO to Playwright (1).
06The evidence ladder
Each row counts the WebdriverIO cases that make that disclosure; the rows are separate counts, ordered from the most basic disclosure to grade A. Of 16 WebdriverIO 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.
Table view
| Item | Count |
|---|---|
| Name a listed framework | 16 |
| Name the client | 10 |
| Publish at least one metric | 14 |
| State a baseline for a metric | 12 |
| State baseline and method for one metric | 2 |
| Reach grade A | 2 |
| Total | 56 |
| Step | WebdriverIO cases | All verified cases |
|---|---|---|
| Name a listed framework | 16 of 16 | 263 of 263 |
| Name the client | 10 of 16 | 91 of 263 |
| Publish at least one metric | 14 of 16 | 210 of 263 |
| State a baseline for a metric | 12 of 16 | 75 of 263 |
| State baseline and method for one metric | 2 of 16 | 35 of 263 |
| Reach grade A | 2 of 16 | 18 of 263 |
07Frameworks named alongside WebdriverIO
16 of 16 cases name at least one other listed framework. The pairing shows which stacks vendors describe together, not which combination works.
Table view
| Item | Count |
|---|---|
| Postman and Newman | 12 |
| Appium | 8 |
| Apache JMeter | 7 |
| Cucumber, SpecFlow, Behave | 3 |
| Cypress | 3 |
| Playwright | 2 |
| Grafana k6 | 1 |
| REST Assured | 1 |
| Total | 37 |
08Where the cases come from
DeviQA (10), a1qa (2) and Abstracta (1) publish the most WebdriverIO cases. A vendor with many cases here shows breadth of published work; the grade columns show how much of it can be checked.
| Vendor | Cases | Grade A or B | With a baselined metric |
|---|---|---|---|
| DeviQA | 10 | 10 | 10 |
| a1qa | 2 | 0 | 0 |
| Abstracta | 1 | 1 | 1 |
| Codoid | 1 | 1 | 1 |
| QAwerk | 1 | 1 | 0 |
| Testrig Technologies | 1 | 0 | 0 |
09What vendors leave out
3 of 16 cases do not state a team size and 12 do not state a duration.
0 of 64 metrics are cost figures and 0 mention flakiness, so maintenance cost and flaky test rates are rarely published.
10Questions for a WebdriverIO proposal
Ask for suite size and run time before and after the work: 5 of 16 cases give no before value for either.
Ask for the flaky test rate over a stated number of runs: 0 of 64 metrics mention flakiness at all.
Ask who owns maintenance after hand-over and what it costs per month: 0 of 64 metrics are cost figures.
Ask for a reference client you can call: 6 of 16 cases keep the client anonymous.
Questions
How many vendors have published WebdriverIO cases?
6 vendors in this dataset, with 16 verified cases between them, as of the dataAsOf date on this page.
How many WebdriverIO cases name the client?
10 of 16. A named client is required for grade A.
Do WebdriverIO case studies publish baselines?
41 of 64 metrics state a before value.
Does this page rank WebdriverIO against other frameworks?
No. The site counts which vendors have evidence on a framework and never compares frameworks.
Records used
This post reads 16 records; the newest verifiedOn date among them sets the data-as-of date.
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
Cypress: what the published cases show
25verified cases
25 verified cases from 10 vendors name Cypress: grades, client types, metric kinds, stacks and the fields vendors leave out.
data as of 2026-11-12 · 25 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
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.