4 posts tagged with "Best Practices"

QA engineers are not test case writers. They're not script generators. They're the people in the room asking "what could go wrong?" before a feature ships — risk assessors, user advocates, and often the only ones who've read the requirements closely enough to notice the gap between what was asked for and what was built. That judgment doesn't live in a test case or a Playwright script. It lives in the person.

This is why the recurring prediction that manual QA is dying has always missed the point. The role isn't defined by its artifacts. It's defined by that instinct — the domain knowledge, the mental model of how real users behave, the memory of what broke last time. Those things are genuinely hard to replace.

The real threat to QA has never been automation. It's been stagnation — testers who stop growing, teams that treat QA as a checkbox, organizations that mistake having a test suite for having a quality culture. That's what erodes the role. Not better tooling.

A few weeks ago, I wrote about bringing your own LLM — choosing your model, using your API key, keeping your data on your infrastructure. But choosing your model was only half the equation. You still couldn't easily tune the prompts that shaped the output.

With v0.14.0, TestPlanIt ships with a full prompt configuration system — every AI prompt visible, editable, and customizable per project, directly in the admin UI.

Every test management vendor is racing to add AI-powered test case generation. And to their credit, most of them aren't charging extra for it — they're bundling it into their existing per-seat pricing. TestRail includes AI in both their Professional ($37/user/month) and Enterprise ($74/user/month) tiers. PractiTest bundles SmartFox AI into their $54/user/month Team plan. BrowserStack includes it in their paid tiers.

So what's the problem?

You're paying for AI whether you use it or not. You don't get to choose the model. You can't see or modify the prompts. You have no control over where your requirements data goes when it's processed. And in some cases — like Qase's credit-based AIDEN system at $0.40 per extra credit — you hit real usage caps when you need it most.

There's a different approach. Plug in your own LLM and API key, choose the model you trust, and keep your data exactly where you want it. Here's why that matters.

If you spend any time in QA forums or Reddit threads, you'll inevitably run into some version of this take: "Test case management tools are outdated. Just use spreadsheets. Or better yet, let your automated tests be your documentation."

And honestly? Those approaches can work. For a while. For small teams.

But they don't scale, and they create problems that only become obvious once you're too deep to easily fix them.