No, not really. Most of those steps are quick, and would have to be done either way. The time savings is in running the test to make sure you didn't screw up something that did work! Otherwise most developers just "hope for the best" and check it in. Even the more motivated ones couldn't hope to redo but a few tests, in comparison to average test harnesses with hundreds to thousands of unit tests.
Any methodology is better than no methodology (?).