Test automation is often treated as a design-time activity. Teams write tests based on requirements, acceptance criteria, or expected user flows, and then rely on those tests to catch regressions as the system evolves. While this approach works to a point, it almost always leaves gaps. Real users behave differently than test designers expect, APIs receive inputs no one planned for, and edge...