Skip to content
Test Automation Vendors / 263 cases

Framework note

Selenium WebDriver: what the published cases show

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

88
verified cases
13
vendors
24 of 88
name the client
46 of 208
metrics with a baseline

88 verified cases in this dataset name Selenium WebDriver, published by 13 vendors. Grades: A 4, B 35, C 49. 24 of 88 name the client, and 46 of 208 published metrics state a baseline.

What stands out

  1. 01Codoid publishes 19 of the 88 Selenium WebDriver cases; the three vendors with the most publish 51, so a reader is looking at a concentrated set of sources.
  2. 0246 of 208 metrics in these cases state a before value; across all 639 metrics in the dataset the count is 209.
  3. 034 of 88 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: 80 of 88 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 Selenium WebDriver, including vendors outside the ranked 12.

Vendors with cases: a1qa (17), Abstracta (2), Codoid (19), DeviQA (10), ImpactQA (2), Qualitest (7), QualityLogic (1), TestDevLab (2), TestFort (15), TestingXperts (2), Testrig Technologies (3), ThinkSys (1) and Zuci Systems (7).

Cases, vendors and grades
Table view
ItemCount
Grade A4
Grade B35
Grade C49
Total88

02Clients and industries

Named clients appear in 24 cases; 64 keep the client anonymous.

Industries stated: Online betting (2), Accounts payable automation (1), Automotive manufacturing (1), Automotive services B2B marketplace (1), Banking and financial services (1), Broadcasting (1), Business community portal (1) and Clinical trial data science (1).

Client types stated: enterprise (11), smb (2) and public (1).

03Metric kinds and baselines

The Selenium WebDriver cases publish 208 metrics. 46 state a baseline and 19 state both a baseline and a method.

  • “Flaky tests cut from 18% to 4.6%”before 18% flaky test rate after 4.6% a1qa a1qa-1 grade B, partial baseline yes method yes
  • “regression testing time was reduced from 5 days to 1.5 days”before 5 days after 1.5 days a1qa a1qa-4 grade B, partial baseline yes method yes
  • “reducing the release cadence from over 1.5 months to just two weeks”before over 1.5 months after two weeks a1qa a1qa-5 grade B, partial baseline yes method yes
  • “established complete test automation infrastructure from zero to 1,000+ tests”before zero after 1,000+ tests a1qa a1qa-5 grade B, partial baseline yes method yes
  • “minimizing scripts code smells from 190 to 1”before 190 after 1 a1qa a1qa-23 grade B, partial baseline yes method yes
  • “Testing is completed faster, within hours rather than days”before days after hours a1qa a1qa-29 grade B, partial baseline yes method yes
Metric kindMetricsWith baseline
other5714
suite-size406
execution-time3820
coverage253
defects242
cost150
release-frequency91

04Languages, CI tools and clouds named alongside

Languages: Java (29), C# (12), Python (7), JavaScript (6), Ruby (5), TypeScript (2), C/C++ (1) and Groovy (1).

CI tools: Jenkins (34), Azure DevOps (9), GitHub Actions (3), Bamboo (2), CircleCI (2), GitLab (2), TeamCity (2) and GoCD (1).

Device or browser clouds: BrowserStack (15), AWS (5), Sauce Labs (3), Azure (1), LambdaTest (1) and TestingBot (1).

05Migration flows

0 cases move a suite to Selenium WebDriver and 3 cases move a suite away from it.

Flows: Selenium WebDriver to Playwright (2) and Selenium WebDriver to Cypress (1).

06The evidence ladder

Each row counts the Selenium WebDriver cases that make that disclosure; the rows are separate counts, ordered from the most basic disclosure to grade A. Of 88 Selenium WebDriver cases, 4 reach grade A, and the rarest disclosure below it is "reach grade a" (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 framework88
Name the client24
Publish at least one metric71
State a baseline for a metric22
State baseline and method for one metric13
Reach grade A4
Total222
StepSelenium WebDriver casesAll verified cases
Name a listed framework88 of 88263 of 263
Name the client24 of 8891 of 263
Publish at least one metric71 of 88210 of 263
State a baseline for a metric22 of 8875 of 263
State baseline and method for one metric13 of 8835 of 263
Reach grade A4 of 8818 of 263

07Frameworks named alongside Selenium WebDriver

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

Frameworks named alongside Selenium WebDriver
Table view
ItemCount
Cucumber, SpecFlow, Behave32
Postman and Newman18
Apache JMeter17
Appium15
REST Assured7
Cypress3
Gatling3
Playwright2
Total97

08Where the cases come from

Codoid (19), a1qa (17) and TestFort (15) publish the most Selenium WebDriver 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
Codoid1952
a1qa1766
TestFort1552
DeviQA1097
Qualitest721
Zuci Systems721
Testrig Technologies311
Abstracta220
ImpactQA220
TestDevLab220
TestingXperts211
QualityLogic111
ThinkSys110

09What vendors leave out

47 of 88 cases do not state a team size and 48 do not state a duration.

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

10Questions for a Selenium WebDriver proposal

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

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

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

Ask for a reference client you can call: 64 of 88 cases keep the client anonymous.

Questions

How many vendors have published Selenium WebDriver cases?

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

How many Selenium WebDriver cases name the client?

24 of 88. A named client is required for grade A.

Do Selenium WebDriver case studies publish baselines?

46 of 208 metrics state a before value.

Does this page rank Selenium WebDriver against other frameworks?

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

Records used

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

Show record ids

a1qa-1, a1qa-4, a1qa-5, a1qa-6, a1qa-14, a1qa-16, a1qa-20, a1qa-21, a1qa-22, a1qa-23, a1qa-26, a1qa-27, a1qa-29, a1qa-38, a1qa-41, a1qa-60, a1qa-63, abstracta-6, abstracta-7, codoid-2, codoid-3, codoid-5, codoid-9, codoid-10, codoid-11, codoid-13, codoid-14, codoid-15, codoid-19, codoid-20, codoid-21, codoid-22, codoid-23, codoid-24, codoid-27, codoid-30, codoid-35, codoid-39, deviqa-4, deviqa-9, deviqa-10, deviqa-14, deviqa-16, deviqa-19, deviqa-28, deviqa-29, deviqa-43, deviqa-49, impactqa-1, impactqa-4, qualitest-2, qualitest-3, qualitest-4, qualitest-5, qualitest-7, qualitest-8, qualitest-10, qualitylogic-3, testdevlab-1, testdevlab-4, testfort-1, testfort-3, testfort-4, testfort-5, testfort-6, testfort-8, testfort-9, testfort-11, testfort-12, testfort-15, testfort-22, testfort-23, testfort-24, testfort-27, testfort-30, testingxperts-4, testingxperts-8, testrig-3, testrig-7, testrig-11, thinksys-8, zuci-systems-1, zuci-systems-2, zuci-systems-4, zuci-systems-5, zuci-systems-6, zuci-systems-7, zuci-systems-8

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

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.