So the answer to “how are we going to verify that vibe-coded application code does what we think it does is “we’re going to vibe-code the tests too”?
In practice, the tests it generates are actually easier to reason about than a lot of hand-written Playwright code I’ve seen in the wild. And for scenarios like acceptance testing or rapid iteration, this approach speeds things up without sacrificing much in terms of clarity or stability.