I thought unit tests was more of a "prevent errors" than "fix errors".
In terms of large projects, I thought unit tests are more for "conforming your modules to design specs" rather than "fixing broken code".
Using Unit Tests to fix code sounds, kinda silly. We have debuggers for that and they work rather well. I thought the reason companies spent so much time on unit tests so that modules written can work everywhere.
Does it waste a lot of valuable time? Hell yeah!
Is it beneficial to large coding groups? Depends.
It is exactly like what the first post stated about JUnit tests, it is just a way to plaster over the cracks of coders merging modules together. Why it takes up soo much development time really just depends on the coders themselves. "Writing tests is just a drag, and so is fixing your code to match those tests. Green checking is just boring... hack-and-slash code to get the green check. Yay!" Just because you hack code together, doesn't make it robust or readable. But, alas, that is what JUnit tests promote when it comes to large coding groups.
We just want to code, not test. What is this, a driving school simulation?