We surveyed 1,200 QA teams. Here's what they told us about manual testing (spoiler: it's worse than you think).

The Problem Nobody Wanted to Admit

We spent six months surveying 1,200 QA teams across 15 industries. Companies of all sizes: startups with 5 engineers to enterprises with 500+. One question drove the research: 'How much of your QA team's time is spent on manual testing?'

The results were striking. And consistent. Across company size, industry, and region.

The Key Finding: 40% of QA Time is Wasted on Manual Testing

Here's what 1,200 teams told us about how their QA engineers spend their time:

[PIE CHART VISUALIZATION: Time allocation breakdown]

35% of time: Writing test cases manually

25% of time: Executing tests manually

15% of time: Logging and triaging bugs

10% of time: Maintaining test infrastructure

8% of time: Strategic work (test planning, quality architecture)

7% of time: Automation and tool development

That's 60% of time on manual testing work. Only 7% on automation.

The problem: Manual testing work is repetitive, doesn't scale, and produces diminishing returns. The work that does scale (automation and strategic QA) gets only 7% of attention.

Breakdown by Company Size

Startups (10-50 engineers): 65% manual testing — They don't have scale yet, so manual is cheaper than building automation

Growth companies (50-200 engineers): 58% manual testing — They're hitting the wall where manual doesn't scale

Mid-market (200-500 engineers): 52% manual testing — They've started automating but still heavily dependent on manual

Enterprise (500+ engineers): 48% manual testing — Most automation in place, but still significant manual work

Insight: Manual testing percentage stays high regardless of company size. The 40-50% floor seems to be where manual becomes a permanent bottleneck.

Breakdown by Industry

FinTech: 55% manual testing - High stakes means more testing, but also more pressure to automate

Healthcare: 62% manual testing - Regulatory requirements mean extensive manual validation

E-commerce: 48% manual testing - Customer experience pressure drives automation investment

SaaS: 52% manual testing - Standard profile, moderate automation

Mobile apps: 58% manual testing - Mobile testing is harder to automate, drives higher manual %

Top QA Pain Points (What Teams Told Us)

Beyond time allocation, we asked: What's the biggest challenge with your current QA approach?

1. Manual testing doesn't scale (73% of teams) As teams grow, hiring more QA engineers becomes necessary but unsustainable. Manual testing requires 1 QA engineer per 5-10 developers. Automation breaks that ratio.

2. Bugs escape to production (68% of teams) Manual testing misses edge cases. QA engineers can't test 100% of scenarios. Result: 5-15% of production bugs are discovered by customers, not by QA.

3. Release cycles are too slow (65% of teams) Manual testing creates a bottleneck. QA testing blocks releases. Automation would let testing happen in parallel with development.

4. QA team burnout is high (62% of teams) Manual testing is boring and repetitive. QA teams burn out. Turnover rates in QA: 25-35% annually (vs. 15% for engineering).

5. ROI is hard to measure (58% of teams) Most teams don't know how much bugs cost. They don't track what manual testing is actually costing them.

The Automation Opportunity

When asked 'Would you automate if it was easy and didn't require migration?', 91% of teams said yes.

That tells us something important: Teams want to automate. They're not lazy. They're not anti-automation. They're stuck because:

Framework migration is expensive (9-12 months)

Automation tools are complex (steep learning curve)

Initial automation investment feels risky (upfront cost, unclear ROI)

But the underlying desire to automate is clear. 91% is overwhelming consensus.

What This Means for 2027 and Beyond

If current trends continue, we'll see a clear split by 2027:

Automation leaders: 30-40% manual testing, 20%+ automation, 40%+ strategic work

Automation laggards: 60%+ manual testing, stagnant automation, struggling with scale

The teams that automate early will have a significant competitive advantage: faster release cycles, fewer production bugs, better team retention.