> I just know intrinsically that they're useless and it's a waste of time. I just know that 95% of my code works and I know what the 5% I'm unsure about is and what manual testing or browser testing I need to do to clarify it.
I'm with you 100% here. I would even go one step further:
Unit tests, where Bob is writing code to test that the code that Bob writes does what Bob wants it to (that's a mouthful), are pointless. They don't test Bob's assumptions, they don't test for correctness, and they don't test for robustness beyond the corner cases Bob can come up with (if Bob bothers to test robustness beyond ensuring that the coverage metrics hit 100%).
Even if Bob comes back in to refactor the code later, the unit tests begin to fail solely because the code has changed locality. That changed locality means that the unit tests have to change as well, invaliding any usefulness of the original unit tests.
I'm with you 100% here. I would even go one step further:
Unit tests, where Bob is writing code to test that the code that Bob writes does what Bob wants it to (that's a mouthful), are pointless. They don't test Bob's assumptions, they don't test for correctness, and they don't test for robustness beyond the corner cases Bob can come up with (if Bob bothers to test robustness beyond ensuring that the coverage metrics hit 100%).
Even if Bob comes back in to refactor the code later, the unit tests begin to fail solely because the code has changed locality. That changed locality means that the unit tests have to change as well, invaliding any usefulness of the original unit tests.