Hey everyone,

I’ve been working as a QA analyst for a little over two years now, and one area I still feel like I’m refining constantly is test case design. Sometimes I get really clear acceptance criteria or requirements, which makes the process straightforward. But other times (more often than I’d like), the specs are either vague or barely exist at all.

When that happens, I find myself relying on instinct, previous bugs I’ve seen, or just walking through the feature manually and hoping I cover all the right scenarios. I know that’s not the most scalable approach, so I’ve been trying to improve my process.

I came across this test case design breakdown recently and found it helpful. It goes over a few techniques that I hadn’t really thought about in a structured way before.

Curious how others here handle this. Do you have a go-to method for designing test cases when documentation is lacking? Do you follow a particular model (like decision tables, boundary value, etc.) or just use exploratory techniques until things feel solid?

Would love to hear how others in QA deal with this.