During Series B due diligence, investors discovered a test suite running 47 minutes while skipping integration tests and covering only 40% of critical paths. The deal proceeded, but with mandatory 90-day remediation.
Why this matters
Investors scrutinize testing maturity because it signals three business outcomes: delivery velocity stability, customer churn patterns, and engineering scalability. A strong test culture means features ship faster with fewer rollbacks, incidents drop.
What investors evaluate
- Test Pyramid Structure: Healthy distributions typically feature 70% unit tests, 25% integration, 5% end-to-end tests, with total runtime under 10 minutes.
- Risk-Based Coverage: Rather than vanity metrics, investors want evidence of protection on revenue-critical flows—checkout, billing, authentication—with dashboards showing specific coverage percentages per system.
- Flake Management: Teams that routinely retry failing tests signal quality theater. Investors expect flakes quarantined within sprints with documented owners.
- Shift-Left Practices: Testing integrated throughout development (pre-commit hooks, PR gates) versus siloed QA phases predicts release cycle duration.
- Production-Parity Environments: Staging should mirror production in configuration, database systems, and data volumes.
Red flags
- Test suites exceeding 30 minutes
- Unmocked external integrations in critical paths
- Minimal payment and authentication coverage
- QA operating as downstream bottleneck rather than team-embedded function
Recommended practices
- Track quality KPIs monthly
- Automate smoke tests for 10–15 revenue journeys completing under 5 minutes
- Ruthlessly disable flaky tests
- Invest in realistic synthetic test data with proper PII masking
Your turn
What testing surprise burned you in a deal? A skipped integration suite? A test that passed locally but failed in CI? Share the scar.
Originally published on the Tech Due Diligence Playbook newsletter on LinkedIn.