On Friday 2015-03-13 15:34 -0700, Gregory Szorc wrote: > 1. Create a commit that introduces a new test > 2. Test it > 3. Create a commit that purportedly fixes the test > 4. Build > 5. Test and verify > 6. Fold the commits
Sure, that's what I'd do in an ideal world. But in reality I sometimes start with 3 (especially if it's a bug that I notice by code inspection), at which point the obvious order to do the rest of the steps quickly and correctly is 1-2-4-5. (And I prefer not to do 6, actually, and to order the test as the earlier commit and then have the code patch actually remove the todo/fails annotation.) -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
signature.asc
Description: Digital signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
