Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

25
  • 94
    What about running your test suite to make sure you didn't break anything? Commented Jun 28, 2016 at 19:32
  • 134
    what if there is no pre-existing test suite? -- How about writing one? Commented Jun 28, 2016 at 20:07
  • 28
    The test suite would definitively help. But the peer review and tests are complementary. I think it's not a good idea to replace one by the other.
    – Christophe
    Commented Jun 28, 2016 at 20:18
  • 8
    @MasonWheeler: Probably a conversation for another time, and you're referring to TDD specifically in that article, using assumptions that I don't think any self-respecting TDD'er would ever make, but I've done it both ways, and I consider the benefits of unit testing to be self-evident. Commented Jun 28, 2016 at 20:24
  • 24
    Merge and hope nothing slips through? That's a notoriously bad idea.
    – Mast
    Commented Jun 29, 2016 at 12:08