Framework note
REST Assured: what the published cases show
Research desk, testautomationvendors.com · published 2026-11-12 · data as of 2026-11-12 · 12 records
- 12
- verified cases
- 7
- vendors
- 4 of 12
- name the client
- 9 of 29
- metrics with a baseline
12 verified cases in this dataset name REST Assured, published by 7 vendors. Grades: A 1, B 8, C 3. 4 of 12 name the client, and 9 of 29 published metrics state a baseline.
What stands out
- 01a1qa publishes 4 of the 12 REST Assured cases; the three vendors with the most publish 8, so a reader is looking at a concentrated set of sources.
- 029 of 29 metrics in these cases state a before value; across all 639 metrics in the dataset the count is 209.
- 031 of 12 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 start year: 10 of 12 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 REST Assured, including vendors outside the ranked 12.
Vendors with cases: a1qa (4), Codoid (1), DeviQA (3), TestDevLab (1), TestFort (1), TestingXperts (1) and Zuci Systems (1).
Table view
| Item | Count |
|---|---|
| Grade A | 1 |
| Grade B | 8 |
| Grade C | 3 |
| Total | 12 |
02Clients and industries
Named clients appear in 4 cases; 8 keep the client anonymous.
Industries stated: Automotive services B2B marketplace (1), Banking (1), Consumer lending (1), Customer experience management software (1), eCommerce (1), EdTech (English learning) (1), EV charging mobile app (1) and Fintech (KYC and AML compliance) (1).
Client types stated: enterprise (1).
03Metric kinds and baselines
The REST Assured cases publish 29 metrics. 9 state a baseline and 5 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
- “cut release decision time from about two working weeks to under one”before about two working weeks after under one working week a1qa a1qa-2 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
- “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
- “The time of testing was reduced by 50%”before Automated test execution took too long to support the delivery process after reduced by 50% DeviQA deviqa-9 grade A, verified baseline baseline yes method yes
- “decreased from 60 minutes to approximately 20 minutes”before 60 minutes after approximately 20 minutes DeviQA deviqa-10 grade B, partial baseline yes method no
| Metric kind | Metrics | With baseline |
|---|---|---|
| other | 7 | 2 |
| execution-time | 6 | 6 |
| coverage | 5 | 0 |
| suite-size | 5 | 1 |
| cost | 3 | 0 |
| defects | 2 | 0 |
| release-frequency | 1 | 0 |
04Languages, CI tools and clouds named alongside
Languages: Java (8), C# (1), Groovy (1) and Python (1).
CI tools: Jenkins (5), Azure DevOps (3), GitHub Actions (1), GitLab CI (1), GoCD (1) and Jenkins CI (1).
Device or browser clouds: BrowserStack (6), AWS (2) and Sauce Labs (2).
05Migration flows
No verified case tags a migration into or out of REST Assured.
06The evidence ladder
Each row counts the REST Assured cases that make that disclosure; the rows are separate counts, ordered from the most basic disclosure to grade A. Of 12 REST Assured cases, 1 reach grade A, and the rarest disclosure below it is "reach grade a" (1 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 | 12 |
| Name the client | 4 |
| Publish at least one metric | 11 |
| State a baseline for a metric | 7 |
| State baseline and method for one metric | 5 |
| Reach grade A | 1 |
| Total | 40 |
| Step | REST Assured cases | All verified cases |
|---|---|---|
| Name a listed framework | 12 of 12 | 263 of 263 |
| Name the client | 4 of 12 | 91 of 263 |
| Publish at least one metric | 11 of 12 | 210 of 263 |
| State a baseline for a metric | 7 of 12 | 75 of 263 |
| State baseline and method for one metric | 5 of 12 | 35 of 263 |
| Reach grade A | 1 of 12 | 18 of 263 |
07Frameworks named alongside REST Assured
12 of 12 cases name at least one other listed framework. The pairing shows which stacks vendors describe together, not which combination works.
Table view
| Item | Count |
|---|---|
| Selenium WebDriver | 7 |
| Apache JMeter | 6 |
| Cucumber, SpecFlow, Behave | 6 |
| Appium | 4 |
| Postman and Newman | 3 |
| Cypress | 1 |
| Playwright | 1 |
| WebdriverIO | 1 |
| Total | 29 |
08Where the cases come from
a1qa (4), DeviQA (3) and Codoid (1) publish the most REST Assured 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 |
|---|---|---|---|
| a1qa | 4 | 3 | 3 |
| DeviQA | 3 | 3 | 2 |
| Codoid | 1 | 1 | 1 |
| TestDevLab | 1 | 1 | 0 |
| TestFort | 1 | 1 | 1 |
| TestingXperts | 1 | 0 | 0 |
| Zuci Systems | 1 | 0 | 0 |
09What vendors leave out
4 of 12 cases do not state a team size and 7 do not state a duration.
3 of 29 metrics are cost figures and 1 mention flakiness, so maintenance cost and flaky test rates are rarely published.
10Questions for a REST Assured proposal
Ask for suite size and run time before and after the work: 7 of 12 cases give no before value for either.
Ask for the flaky test rate over a stated number of runs: 1 of 29 metrics mention flakiness at all.
Ask who owns maintenance after hand-over and what it costs per month: 3 of 29 metrics are cost figures.
Ask for a reference client you can call: 8 of 12 cases keep the client anonymous.
Questions
How many vendors have published REST Assured cases?
7 vendors in this dataset, with 12 verified cases between them, as of the dataAsOf date on this page.
How many REST Assured cases name the client?
4 of 12. A named client is required for grade A.
Do REST Assured case studies publish baselines?
9 of 29 metrics state a before value.
Does this page rank REST Assured against other frameworks?
No. The site counts which vendors have evidence on a framework and never compares frameworks.
Records used
This post reads 12 records; the newest verifiedOn date among them sets the data-as-of date.
Show record ids
a1qa-1, a1qa-2, a1qa-4, a1qa-66, codoid-1, deviqa-9, deviqa-10, deviqa-25, testdevlab-4, testfort-8, testingxperts-7, zuci-systems-7
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.