How to read a QA vendor case study

Read a case study field by field: who the client is, what was tested, for how long, with what team, what changed in numbers, and when it was published. Below, the same 10 fields are applied to three case studies from the corpus with different grades.

The 10 fields

Title, client, systems, testing types, scope, team and stack, outcomes, date published, source URL, scope notes. A field the text does not state stays empty and is listed as not stated. Nothing is inferred to fill a field.

Three case studies, three grades

A Discover How ImpactQA Helped a Leading Logistics Firm in Accelerating the Operational Efficiency by 60% (ImpactQA, grade A)

1 TitleDiscover How ImpactQA Helped a Leading Logistics Firm in Accelerating the Operational Efficiency by 60% ev-0502
2 ClientDTDC ev-0504
3 SystemsNot stated
4 Testing typesNot stated
5 ScopeQA of the client's product application and its module architecture by a dedicated QA team, covering the whole testing process and a review of the QA process. Engagement length is not stated. The full case study is a gated download; only the landing page text is recorded.
6 Team and stackNot stated
7 Outcomes
  • operational efficiency accelerated by 60%: Accelerating the Operational Efficiency by 60%ev-0506
8 Date published2021-05-26 (page metadata)ev-0509
9 Source URLhttps://www.impactqa.com/case-studies/dtdc/
10 Scope notes
  • our team identified lack of streamlined QA process in their product catalogue as publishedev-0507
  • highlighted a vast scope of process improvement as publishedev-0508

Not stated: Which logistics system was tested; Which testing types were used; How long the engagement lasted; Team size and tools.

B Complex QA support for a global manufacturer of electric vehicles (a1qa, grade B)

1 TitleComplex QA support for a global manufacturer of electric vehicles ev-0028
2 Clientanonymised by vendor: "a global manufacturer of electric vehicles" ev-0030
3 Systemsfleet and telematicsev-0031
4 Testing typestest automationev-0032 performance and peak loadev-0033 mobile and handheldev-0034 functionalintegration (vehicle subsystems)
5 ScopeFunctional, integration, performance and automated testing across three streams for an electric vehicle maker: car systems, business systems (CRM, ERP), and web and mobile B2B apps including a bus park management platform and fleet logistics and management solutions. Engagement stated as 1.5 years.
Engagement length as stated: 1.5 years of project durationev-0040
6 Team and stack19 engineers at peak; Java, Kotlin, Python, Playwright, CodeceptJS, TestRail, Allure, JUnit, Kotest, Docker, Kubernetes, Apache Kafka and othersev-0041
7 Outcomes
  • 5 days on average to staff a new position: 5 days on average to staff a new positionev-0037
8 Date published2025-07-08 (page metadata)ev-0042
9 Source URLhttps://www.a1qa.com/portfolio/thorough-qa-for-commercial-ev-producer/
10 Scope notes
  • Sped up quality control activities due to automating workflows within all subprojects as publishedev-0038
  • such as a bus park management platform, customer care portal as publishedev-0039

Not stated: The client's name.

C Daylight Transport (auticon, grade C)

1 TitleDaylight Transport ev-0152
2 ClientDaylight Transport ev-0154
3 SystemsTMSev-0155
4 Testing typestest automationev-0156 manualregression
5 ScopeQA support for several internal systems of a US less-than-truckload carrier, including five web portals and a custom LTL transport management system: definition of the QA approach, test case and regression suite development, test script execution and support of issue resolution, with collaboration stated as running since 2019.
Engagement length as stated: since 2019 (ongoing at publication on 2026-05-22; months is a lower bound from the stated year)ev-0162
6 Team and stackNot stated
7 OutcomesNot stated
8 Date published2026-05-22 (page metadata)ev-0163
9 Source URLhttps://auticon.com/blog/portfolio/daylight-transport/
10 Scope notes
  • Improved product quality and release efficiency as publishedev-0158
  • Long-term regression testing suite implemented as publishedev-0159
  • Five web portals and one transport management system supported as publishedev-0160
  • Trusted partner across multiple projects as publishedev-0161

Not stated: Team size and tools; Any quantified outcome.

Questions to ask the vendor

For every field listed as not stated, ask the vendor for it directly. For outcomes, ask how the figure was measured and over which period. The case study index shows all recorded case studies with their grades.

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