<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Test Automation Vendors: blog</title>
  <subtitle>Posts computed from graded test automation case studies.</subtitle>
  <link href="https://testautomationvendors.com/blog/feed.xml" rel="self"/>
  <link href="https://testautomationvendors.com/blog/"/>
  <id>https://testautomationvendors.com/blog/</id>
  <updated>2026-11-12T00:00:00Z</updated>
  <author><name>Research desk, testautomationvendors.com</name></author>
  <entry>
    <title>Playwright: what the published cases show</title>
    <link href="https://testautomationvendors.com/blog/playwright-what-the-cases-show/"/>
    <id>https://testautomationvendors.com/blog/playwright-what-the-cases-show/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="framework-note"/>
    <summary>48 verified cases from 14 vendors name Playwright: grades, client types, metric kinds, stacks and the fields vendors leave out.</summary>
  </entry>
  <entry>
    <title>Cypress: what the published cases show</title>
    <link href="https://testautomationvendors.com/blog/cypress-what-the-cases-show/"/>
    <id>https://testautomationvendors.com/blog/cypress-what-the-cases-show/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="framework-note"/>
    <summary>25 verified cases from 10 vendors name Cypress: grades, client types, metric kinds, stacks and the fields vendors leave out.</summary>
  </entry>
  <entry>
    <title>Selenium WebDriver: what the published cases show</title>
    <link href="https://testautomationvendors.com/blog/selenium-what-the-cases-show/"/>
    <id>https://testautomationvendors.com/blog/selenium-what-the-cases-show/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="framework-note"/>
    <summary>88 verified cases from 13 vendors name Selenium WebDriver: grades, client types, metric kinds, stacks and the fields vendors leave out.</summary>
  </entry>
  <entry>
    <title>WebdriverIO: what the published cases show</title>
    <link href="https://testautomationvendors.com/blog/webdriverio-what-the-cases-show/"/>
    <id>https://testautomationvendors.com/blog/webdriverio-what-the-cases-show/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="framework-note"/>
    <summary>16 verified cases from 6 vendors name WebdriverIO: grades, client types, metric kinds, stacks and the fields vendors leave out.</summary>
  </entry>
  <entry>
    <title>Appium: what the published cases show</title>
    <link href="https://testautomationvendors.com/blog/appium-what-the-cases-show/"/>
    <id>https://testautomationvendors.com/blog/appium-what-the-cases-show/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="framework-note"/>
    <summary>47 verified cases from 10 vendors name Appium: grades, client types, metric kinds, stacks and the fields vendors leave out.</summary>
  </entry>
  <entry>
    <title>REST Assured: what the published cases show</title>
    <link href="https://testautomationvendors.com/blog/rest-assured-what-the-cases-show/"/>
    <id>https://testautomationvendors.com/blog/rest-assured-what-the-cases-show/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="framework-note"/>
    <summary>12 verified cases from 7 vendors name REST Assured: grades, client types, metric kinds, stacks and the fields vendors leave out.</summary>
  </entry>
  <entry>
    <title>Postman and Newman: what the published cases show</title>
    <link href="https://testautomationvendors.com/blog/postman-what-the-cases-show/"/>
    <id>https://testautomationvendors.com/blog/postman-what-the-cases-show/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="framework-note"/>
    <summary>98 verified cases from 9 vendors name Postman and Newman: grades, client types, metric kinds, stacks and the fields vendors leave out.</summary>
  </entry>
  <entry>
    <title>Apache JMeter: what the published cases show</title>
    <link href="https://testautomationvendors.com/blog/jmeter-what-the-cases-show/"/>
    <id>https://testautomationvendors.com/blog/jmeter-what-the-cases-show/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="framework-note"/>
    <summary>63 verified cases from 12 vendors name Apache JMeter: grades, client types, metric kinds, stacks and the fields vendors leave out.</summary>
  </entry>
  <entry>
    <title>Cucumber, SpecFlow, Behave: what the published cases show</title>
    <link href="https://testautomationvendors.com/blog/cucumber-bdd-what-the-cases-show/"/>
    <id>https://testautomationvendors.com/blog/cucumber-bdd-what-the-cases-show/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="framework-note"/>
    <summary>53 verified cases from 9 vendors name Cucumber, SpecFlow, Behave: grades, client types, metric kinds, stacks and the fields vendors leave out.</summary>
  </entry>
  <entry>
    <title>How often published automation case studies state a baseline</title>
    <link href="https://testautomationvendors.com/blog/how-often-automation-case-studies-state-a-baseline/"/>
    <id>https://testautomationvendors.com/blog/how-often-automation-case-studies-state-a-baseline/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="pattern"/>
    <summary>Of 263 verified automation cases, 75 state a before value for at least one metric. Counts by vendor and metric kind.</summary>
  </entry>
  <entry>
    <title>Execution time claims across published cases: with and without baselines</title>
    <link href="https://testautomationvendors.com/blog/execution-time-claims-with-and-without-baselines/"/>
    <id>https://testautomationvendors.com/blog/execution-time-claims-with-and-without-baselines/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="pattern"/>
    <summary>120 execution time claims from verified automation cases, split by whether the vendor states the before value.</summary>
  </entry>
  <entry>
    <title>Named versus anonymous clients in automation case studies, by vendor</title>
    <link href="https://testautomationvendors.com/blog/named-versus-anonymous-clients-by-vendor/"/>
    <id>https://testautomationvendors.com/blog/named-versus-anonymous-clients-by-vendor/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="pattern"/>
    <summary>91 of 263 verified automation cases name the client. Counts per vendor.</summary>
  </entry>
  <entry>
    <title>Team sizes vendors disclose in automation engagements</title>
    <link href="https://testautomationvendors.com/blog/team-sizes-in-automation-engagements/"/>
    <id>https://testautomationvendors.com/blog/team-sizes-in-automation-engagements/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="pattern"/>
    <summary>149 of 263 verified automation cases state a team size. The distribution and the cases.</summary>
  </entry>
  <entry>
    <title>Engagement lengths disclosed in automation cases</title>
    <link href="https://testautomationvendors.com/blog/engagement-lengths-in-automation-cases/"/>
    <id>https://testautomationvendors.com/blog/engagement-lengths-in-automation-cases/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="pattern"/>
    <summary>109 of 263 verified automation cases state the engagement length. Distribution and cases.</summary>
  </entry>
  <entry>
    <title>What migrations vendors publish: from and to, counted</title>
    <link href="https://testautomationvendors.com/blog/what-migrations-vendors-publish/"/>
    <id>https://testautomationvendors.com/blog/what-migrations-vendors-publish/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="pattern"/>
    <summary>11 verified automation cases describe moving a test suite between frameworks. Flows counted.</summary>
  </entry>
  <entry>
    <title>Coverage claims in automation cases: how many define the denominator</title>
    <link href="https://testautomationvendors.com/blog/coverage-claims-and-their-denominators/"/>
    <id>https://testautomationvendors.com/blog/coverage-claims-and-their-denominators/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="pattern"/>
    <summary>88 coverage claims from verified automation cases, sorted by whether the quote says what the figure is a share of.</summary>
  </entry>
  <entry>
    <title>Languages paired with each web framework in published cases</title>
    <link href="https://testautomationvendors.com/blog/languages-paired-with-web-frameworks/"/>
    <id>https://testautomationvendors.com/blog/languages-paired-with-web-frameworks/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="pattern"/>
    <summary>139 verified cases name a programming language. Pairings with each web UI framework, counted.</summary>
  </entry>
  <entry>
    <title>CI tools named in automation cases</title>
    <link href="https://testautomationvendors.com/blog/ci-tools-named-in-automation-cases/"/>
    <id>https://testautomationvendors.com/blog/ci-tools-named-in-automation-cases/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="pattern"/>
    <summary>127 verified automation cases name a CI tool. Counts per tool and per vendor.</summary>
  </entry>
  <entry>
    <title>Industries that appear in automation case studies</title>
    <link href="https://testautomationvendors.com/blog/industries-in-automation-case-studies/"/>
    <id>https://testautomationvendors.com/blog/industries-in-automation-case-studies/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="pattern"/>
    <summary>Industries stated across 263 verified automation cases, counted.</summary>
  </entry>
  <entry>
    <title>How to read a test automation case study: the fields that are usually missing</title>
    <link href="https://testautomationvendors.com/blog/how-to-read-a-test-automation-case-study/"/>
    <id>https://testautomationvendors.com/blog/how-to-read-a-test-automation-case-study/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="buyer"/>
    <summary>Field by field, how often 263 verified automation cases leave out team size, duration, baseline, client name and CI.</summary>
  </entry>
  <entry>
    <title>Why a percentage without a baseline is a claim, not a result</title>
    <link href="https://testautomationvendors.com/blog/percentage-without-baseline-is-a-claim/"/>
    <id>https://testautomationvendors.com/blog/percentage-without-baseline-is-a-claim/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="buyer"/>
    <summary>246 percentage claims in verified automation cases, and how many state the starting value.</summary>
  </entry>
  <entry>
    <title>What an automation coverage figure can mean: the denominators seen in published cases</title>
    <link href="https://testautomationvendors.com/blog/what-an-automation-coverage-figure-can-mean/"/>
    <id>https://testautomationvendors.com/blog/what-an-automation-coverage-figure-can-mean/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="buyer"/>
    <summary>88 coverage claims sorted by what they measure: test cases, regression effort, features or code.</summary>
  </entry>
  <entry>
    <title>Questions to ask a vendor about a migration case before you rely on it</title>
    <link href="https://testautomationvendors.com/blog/questions-to-ask-about-a-migration-case/"/>
    <id>https://testautomationvendors.com/blog/questions-to-ask-about-a-migration-case/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="buyer"/>
    <summary>What 11 published migration cases disclose and leave out, turned into questions for the vendor.</summary>
  </entry>
  <entry>
    <title>RFP questions per framework layer, derived from what cases disclose</title>
    <link href="https://testautomationvendors.com/blog/rfp-questions-per-framework-layer/"/>
    <id>https://testautomationvendors.com/blog/rfp-questions-per-framework-layer/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="buyer"/>
    <summary>Request-for-proposal questions for web UI, mobile, API and performance automation, each tied to a disclosure gap counted in published cases.</summary>
  </entry>
  <entry>
    <title>Flakiness claims: how cases describe them and what to ask for</title>
    <link href="https://testautomationvendors.com/blog/flakiness-claims-in-automation-cases/"/>
    <id>https://testautomationvendors.com/blog/flakiness-claims-in-automation-cases/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="buyer"/>
    <summary>4 metrics in verified automation cases mention flaky or unstable tests.</summary>
  </entry>
  <entry>
    <title>Team size and ramp-up: what disclosed cases show</title>
    <link href="https://testautomationvendors.com/blog/team-size-and-ramp-up-in-disclosed-cases/"/>
    <id>https://testautomationvendors.com/blog/team-size-and-ramp-up-in-disclosed-cases/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="buyer"/>
    <summary>149 verified automation cases state a team size; what they say about ramp-up.</summary>
  </entry>
  <entry>
    <title>Device and browser clouds named in cases, and what that implies for your bill</title>
    <link href="https://testautomationvendors.com/blog/device-and-browser-clouds-named-in-cases/"/>
    <id>https://testautomationvendors.com/blog/device-and-browser-clouds-named-in-cases/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="buyer"/>
    <summary>79 verified automation cases name a device or browser cloud.</summary>
  </entry>
  <entry>
    <title>How this ranking grades a case: A, B, C and X with real examples</title>
    <link href="https://testautomationvendors.com/blog/how-this-ranking-grades-a-case/"/>
    <id>https://testautomationvendors.com/blog/how-this-ranking-grades-a-case/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-11T00:00:00Z</updated>
    <category term="buyer"/>
    <summary>Grade rules with examples from 263 verified cases: A 18, B 108, C 137; 0 removed as X.</summary>
  </entry>
  <entry>
    <title>What this ranking cannot tell you, and where to get it</title>
    <link href="https://testautomationvendors.com/blog/what-this-ranking-cannot-tell-you/"/>
    <id>https://testautomationvendors.com/blog/what-this-ranking-cannot-tell-you/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-11T00:00:00Z</updated>
    <category term="buyer"/>
    <summary>Service quality, current staff and pricing are outside the data; where to look instead.</summary>
  </entry>
  <entry>
    <title>Reading a Clutch review for framework evidence</title>
    <link href="https://testautomationvendors.com/blog/reading-a-clutch-review-for-framework-evidence/"/>
    <id>https://testautomationvendors.com/blog/reading-a-clutch-review-for-framework-evidence/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <category term="buyer"/>
    <summary>Collectors kept only verified third-party reviews whose text names a listed framework: 17 across 6 of 17 vendors.</summary>
  </entry>
  <entry>
    <title>How to request a correction and what gets logged</title>
    <link href="https://testautomationvendors.com/blog/how-to-request-a-correction/"/>
    <id>https://testautomationvendors.com/blog/how-to-request-a-correction/</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-11T00:00:00Z</updated>
    <category term="buyer"/>
    <summary>The correction process for vendors and readers, and what the changelog records.</summary>
  </entry>
</feed>
