How to verify a QA vendor case study yourself

Every case study in this ranking passed the same checks: the page is on the vendor's own domain, it describes testing work, it names a logistics system or client, and every quoted figure is on the page. You can run the same checks in a few minutes.

The checks

  1. Domain: the case study URL is on the vendor's own domain. Listings on directories do not count.
  2. Testing work: the text describes testing activities, test types or a testing outcome. A team list with one QA role is not enough.
  3. Logistics: the text names a system (WMS, TMS, fleet, last-mile, freight, EDI) or a logistics client such as a 3PL, carrier or courier.
  4. Client: the client is named in the text, not only shown as a logo.
  5. Figures: each outcome has a number and a unit; note the period it covers.
  6. Date: a visible date or a date in the page metadata. Undated pages lose one grade here.

What the corpus looks like after these checks

In the recorded corpus of 29 case studies: grade A 2, grade B 12, grade C 15; 7 carry no publication date and lost one grade step.

The same checks per ranked vendor, from the recorded corpus:

VendorABCUndatedNamed client
N-iX11101
a1qa03000
Qualitest02000
ScienceSoft00200
DeviQA00333
Crestech03000
HCLTech02100
ImpactQA10001
Codoid00330
TestingXperts01000
BugRaptors00110
auticon00202
Mindfire Solutions00200

Then grade it

Apply grade A, B or C as in the methodology and compare with the grade this site shows on the case study index.

Scenario rankings: all scenario rankings. Method: methodology. Data: case study index, ranking, downloads.

Sources

    Scores are computed from vendors' published case studies and third-party reviews by the methodology on this site, frozen on the date shown. Case study outcomes are quoted as published by the vendor and are not verified results. Absence of evidence is not evidence of absence. This site does not accept payment from vendors.

    Suggest a case study or correction