Throughout my career, I’ve held many roles in the QA conversation: As a developer, waiting on test teams to validate features before a release could ship As a tech lead, watching sprint capacity dwindle while we converted Jira stories into test cases by hand As an architect, auditing a test repository with 4,000 cases where no one knew which ones matteredSo when “AI test generation” started appearing as part of every testing product, I was both interested…and skeptical. After spending time with several of these tools, I’ve decided that the phrase “AI test generation” covers two fundamentally different architectures.