On Tuesday 28 March 2006 17:53, Neal Norwitz wrote: > In order to do the best possible job and avoid silly errors, there > shouldn't be any checkins which could change behaviour that do not > include a test. I'm not talking about updating comments or string > constants. But even trivial changes can cause regressions or > incompatible changes. Just like failing tests, code checked in > without tests is fair game for being reverted if there is anything > questionable. +1 from me. Anyone disagree? Anthony -- Anthony Baxter <anthony at interlink.com.au> It's never too late to have a happy childhood.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4