Skip to main content
Software Engineering

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.

5
  • Good answer, but note that newly written code passing all tests isn't the same as it being bug-free. In particular you might have overlooked specific edge-cases - both in terms of coding and testing. Commented Jun 2 at 11:05
  • Yeah, I tried to be careful with the wording here. "freshly written code could be more or less bug-free" Commented Jun 2 at 13:26
  • I think I understand your intent - though I feel "newly written code doesn't have bugs" and "breakage could appear in the future" are at odds with each other. Wouldn't breakage occur from newly written code ? Commented Jun 2 at 15:22
  • @aaaaaa: Perhaps the more verbose way of stating is that "newly written code could be more or less bug-free, further newer code changes could cause breakage of less newly written and working code.". Commented Jun 2 at 21:44
  • #2 all the way. Of course this assumes that all the edge cases were covered. If they aren't then you have just discovered a new edge case to add to the unit tests, which is how successful open source projects manage it. Commented Jun 2 at 23:32