Commit 60835490 authored by David Benn's avatar David Benn Committed by Maxim Belkin
Browse files number of possible interactions between bugs in code (#706)

parent 242bb2e8
......@@ -140,7 +140,7 @@ we want to localize the failure to the smallest possible region of code:
then concentrate on either the first or second half,
and so on.
2. N things can interact in N<sup>2</sup> different ways,
2. N things can interact in N! different ways,
so every line of code that *isn't* run as part of a test
means more than one thing we don't need to worry about.
......@@ -162,7 +162,7 @@ however small,
we should re-run our tests immediately,
because the more things we change at once,
the harder it is to know what's responsible for what
(those N<sup>2</sup> interactions again).
(those N! interactions again).
And we should re-run *all* of our tests:
more than half of fixes made to code introduce (or re-introduce) bugs,
so re-running all of our tests tells us whether we have regressed.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment