nbaugh1 parent
Not at all. Submitting untested PRs is a wildly outside of my experience. Having tests written to cover your code is a pre-requisite for having your PR reviewed on our team. "Does it work" aka passing manual testing, is literally the bare minimum before submitting a PR
If it's all vibe coded, how do you know — without review — that the new tests, for a new feature, test anything useful at all?
We don't, that's why we do review it. We also do things like communicate with teammates, have expectations of not wasting other people's time, and try to uphold standards and meet SLAs. Maybe people should worry about why their teams are so dysfunctional rather than how the code was produced
When I was in a test-driven development environment, one of our rules was that you had to see the test fail. You had to prove that it would actually test what you were trying to test.