Breaknorm
Sign inStart free

Product

SignalsPeopleCompaniesLocal businessesMCP and API

Plays

Post engagersTeam build-outChampion movedHiring surgeNewly fundedLookalikesAll plays

Data

Coverage by countryHiring dataJob changesEmail verificationCompanies by toolWho is hiringMarket mapsOutboundCompany profilesCompare
PricingDatasetsDocsSign in
Compare · unit testing frameworks

GoogleTest VS React Testing Library

As of 30 October 2026, React Testing Library is named by 335 companies and GoogleTest by 138; GoogleTest skews to companies under 200 people (38% vs 57%), React Testing Library to companies over 1,000 (20% vs 40%).

As of 30 October 2026 · refreshed daily · counts move as websites, DNS and career sites are re-read.

The website-and-DNS footprint is not comparable between a marketing suite and a CRM: GoogleTest's script and mail records show on hundreds of thousands of small sites, React Testing Library rarely leaves a trace outside its own apps. Compare on the job-posting numbers; use the footprint for reach.

GoogleTest: 2–200 employees
38%
React Testing Library: 2–200 employees
57%
GoogleTest: 1,000+ employees
40%
React Testing Library: 1,000+ employees
20%
Postings per company, 90 days
2.3 · 2.1
Website or DNS footprint
0 · 0
138companies name GoogleTest
335companies name React Testing Library
0name both
324 · 716postings in 90 days, GoogleTest · React Testing Library
02Side by side

Who chooses which

Share of each tool's companies in every segment. "Leans" marks a gap of more than two points.

By company size
SegmentGoogleTestshareReact Testing LibraryshareLeans
Self-employed21%51%even
2-10 employees75%4112%React Testing Library
11-50 employees1410%7522%React Testing Library
51-200 employees3122%7522%even
201-500 employees1813%4814%even
501-1000 employees118%237%even
1001-5000 employees2115%4112%GoogleTest
5001-10000 employees97%72%GoogleTest
10,001+ employees2518%206%GoogleTest
By industry
SegmentGoogleTestshareReact Testing LibraryshareLeans
Manufacturing & industry6245%185%GoogleTest
Technology & software3626%20461%React Testing Library
Business & finance services1511%6519%React Testing Library
Automotive64%21%GoogleTest
Media & content54%103%even
Public, community & associations32%21%even
Consumer services & leisure32%72%even
Utilities & infrastructure32%31%even
Commerce & trade21%154%React Testing Library
Hospitality & travel11%10%even
Property & construction11%––outside top 12
Transport, logistics & rental11%41%even
Health care––41%outside top 12
By country
SegmentGoogleTestshareReact Testing LibraryshareLeans
United States8562%19257%GoogleTest
Germany1410%103%GoogleTest
Poland75%51%GoogleTest
Canada64%93%even
United Kingdom64%3510%React Testing Library
France43%82%even
Netherlands43%––outside top 12
India32%227%React Testing Library
Austria21%––outside top 12
Sweden21%––outside top 12
Australia11%51%even
Denmark11%––outside top 12
Singapore––51%outside top 12
Lithuania––41%outside top 12
United Arab Emirates––31%outside top 12
Brazil––31%outside top 12
Postings by team (share of each tool's postings)
SegmentGoogleTestshareReact Testing LibraryshareLeans
Software engineering37482%89194%React Testing Library
Engineering (non-software)194%91%GoogleTest
Data & AI61%40%even
IT operations & business systems31%81%even
Product, program & project management20%––outside top 12
Research and science10%––outside top 12
Customer service & success––20%outside top 12
Design & UX––10%outside top 12
Quality, safety & environment––10%outside top 12
Sales––10%outside top 12
Unclassified––10%outside top 12
Cite this

Quote the sentence with the date and the link. The numbers change daily; the link always shows the current ones.

React Testing Library is named by 335 companies in job postings and GoogleTest by 138; 0 name both. (Breaknorm, 30 October 2026, https://breaknorm.co/compare/googletest-vs-react-testing-library)
How we know

Read from the source, not self-reported

Every number on this page can be traced to a page we crawled or a posting we read. Full methodology →

  • Job postingsRead hourly from career sites. A tool counts when the employer's own text names it as the team's system; both tools can count for one company.
  • Website and DNSScripts and embeds on the company's pages, plus SPF, DKIM, MX and CNAME records of its domain that point at the vendor.
  • SegmentsCountry, size and industry from the company profile built from its website.
  • Not a reviewNo ratings, prices or feature claims. For those, read the vendors.
FAQ

GoogleTest vs React Testing Library: questions

Which is more used, GoogleTest or React Testing Library?

By companies naming it in their own job postings, React Testing Library (335) over GoogleTest (138). By website-and-DNS footprint, React Testing Library (0 vs 0), because its scripts and mail records sit on many small company sites.

Who chooses GoogleTest?

38% of GoogleTest companies have 2 to 200 employees, against 57% for React Testing Library. 40% of GoogleTest companies have over 1,000 employees, against 20% for React Testing Library.

Do companies run both?

0 companies name both in their postings, usually GoogleTest in marketing and React Testing Library in sales, or during a migration.

Where do these numbers come from?

From the employer's own text in job postings read hourly from career sites, and from scripts found on company websites in our crawl. No vendor data, no surveys.

Companies and people

Get either list your way

The same data as a search, over MCP and the API, as bulk files, or pushed to you as it changes.

Every company on either tool,
with the person who owns it

Filter on GoogleTest or React Testing Library. Start free, no card.

  1. 01Sign up, no card
  2. 02Connect Claude, ChatGPT or an API key
  3. 03Ask for your market