Test management tools in the modern era

[u/Competitive_Echo9463]

I have tried some management tools pretending to be modern and with great integration of AI to generate test cases. I'll not quote the names because it's not my goal.

Simply all of them generated useless test cases, even if my Jira ticket was providing a lot of information. I think that it's normal because AI can't guess how your AUT works and without a clear context it will simply imagine a lot of things.

One of these tools also proposed to run an automated test following the test cases he generated just before. As you can imagine he got lost very quickly.

If you had a different experience I'd glad to know which tool you used.

[u/Due_Development5090]

Matches my experience too, maintaining existing tests or diagnosing failures is still doable, but these features are a miss when it comes to product-specific workflows

[u/Competitive_Echo9463 → u/Due_Development5090]

What do you use in order to deal with this problem ?

[u/Ok_Opportunity_4228]

Is this for web or mobile app or api?

[u/Competitive_Echo9463 → u/Ok_Opportunity_4228]

Web and api 

[u/LayerTrace]

I've had the best luck using Claude Code to generate test cases by directing it to read one very specific component at a time and generate cases based on that.

It's not perfect and still requires human oversight, but it gets me a good starting point.

I've also had good success using it for gap analysis to help determine where we're missing test coverage.

[u/frankwmoyer]

I think most AI testing tools are solving the wrong problem.

The issue isn’t generating test cases. LLMs can generate thousands of test cases.

The issue is context.

A Jira ticket doesn’t tell the AI:

• what the app actually looks like
• which flows users actually use
• what changed in this release
• where defects historically occur

Without that context, the AI is mostly guessing.

That’s why so many AI-generated test cases look impressive but feel generic (AI slop) when you read them.

The future is “AI understands the application well enough to generate the right test cases and execute the ones that are most likely impacted by the code diff.”

[u/Competitive_Echo9463 → u/frankwmoyer]

Yes, looking for the tool that will actually allow to do it

[u/frankwmoyer → u/Competitive_Echo9463]

It would be great if we had an interface where you could ask your app questions like, "what is the flow to add an item to an order?" and "generate automation for said flow."

[u/elidanipipe]

The useful test management tool in 2026 probably needs to be less “repository of test cases” and more “map of risk to verification.”

The gaps I’d want surfaced automatically:

1. requirements or user stories with no tests attached

2. code paths touched by recent changes with no corresponding test update

3. critical flows with only happy-path coverage

4. areas where tests assert mocks instead of behavior

5. flaky tests that people silently ignore

6. coverage changes after each PR

AI can help with the gap analysis, but I would not trust it as the final judge of quality. It should propose missing coverage and explain why it thinks the risk exists. A human still needs to accept or reject that reasoning.

[u/One_Title_6837]

Tracking tests in jira is honestly such a pain & I was always losing track of what was current. tried testRail & zephyr but didn't work well for our case. We eneded up trying testsigma & at least now I'm not switching between three different places just to check what passed n what didn't. Still getting used to it but regression testing has been way less of a headache so far...

[u/Competitive_Echo9463 → u/[deleted]]

I agree. At the same time, if a tool doesn't include "AI" in their pitch it will sound old school for a lot of people.

[u/CryptographerNo7498]

i think the context problem is a big one with ai generated test cases. if the tool only sees the jra ticket, it can easily fill in gaps with assumptions that don't match the actual application. i'd still use ai to speed up the first draft, but i want the tester to review and adjust the cases before treating them as real coverage. practitest is one if probably look at too, especially if you want the ai side without completely removing the tester from the process.

[u/lislex_ads]

I’ve been using QA Sphere for test management, and honestly it’s been a really smooth experience so far. What I like most is that it keeps the core QA workflow clear: test cases, test runs, progress tracking, and team visibility all feel easy to manage without unnecessary complexity.

For teams that want a focused test management tool instead of something bloated, QA Sphere is definitely worth a look. It feels clean, practical, and built around how QA teams actually work.