Mak Mo

๐Ÿงช QA Teams: How do you handle regression testing with 1000+ test cases?

Hey Product Hunt community! ๐Ÿ‘‹

I'm researching how QA teams manage regression testing when dealing with massive test suites (1000+ test cases). Currently building a tool to help automate test selection, but want to understand real-world pain points first.

## Quick poll: What's your current approach?

Option A: Run the full suite every time (and cry about CI times) ๐Ÿ˜ญ

Option B: Manually cherry-pick tests based on gut feeling ๐ŸŽฏ

Option C: Use some form of automated selection/prioritization ๐Ÿค–

Option D: Split into smoke/critical/full suites ๐Ÿ“Š

Option E: Other (please share!) ๐Ÿ”ฅ

## Specific questions I'm curious about:

1. Time constraints: How long can your CI/CD pipeline realistically wait for regression tests?

2. Selection criteria: When manually choosing tests, what factors do you consider? (file changes, risk areas, historical failures, etc.)

3. Pain points: What's the biggest challenge - time, accuracy, or something else?

4. False confidence: Ever had a "green" pipeline that still shipped bugs because you didn't run the right tests?

5. Team size: How many people are involved in test selection decisions?

## Context:

Working on an MVP that analyzes PR changes and recommends relevant tests from your existing suite. Think "smart test selection" rather than "run everything or guess."

Especially interested in hearing from:

- QA Engineers managing large test suites

- Engineering managers dealing with slow CI pipelines

- Teams using TestRail, Jira, or similar test management tools

- Anyone who's tried test impact analysis tools

## What would make your life easier?

Drop your experiences below! Even if it's just "we run everything and it takes 6 hours" - that's valuable data.

Looking to validate whether automated test selection is solving a real problem or if I'm building something nobody actually needs. ๐Ÿคทโ€โ™‚๏ธ

---

Building in public and would love to get this right. Will share learnings back with the community!

#QA #Testing #DevOps #CI #BuildingInPublic

3 views

Add a comment

Replies

Be the first to comment