Hi, On Tue, 27 Feb 2007, Junio C Hamano wrote: > Sam Vilain <sam@xxxxxxxxxx> writes: > > > Junio C Hamano wrote: > >> I take that as a sign that git hasn't been exercised well and > >> yet more ancient bugs are sleeping, waiting to be triggered, not > >> as a sign that we are very careful and adding only small number > >> of risky new code in the releases. > >> > > > > No! It's a sign that there aren't enough tests :) > > > > Maybe investigate the coverage of the test suite? > > I know we cover most of the success (expected) cases for things > we care about, but at the same time I personally find that tests > for failure cases (insane input, dataset expected to fail) are > missing. > > We do not need investigation. We need a volunteer. Maybe a Summer of Code project? > And perhaps a new patch/feature acceptance criteria that requires both > expected behaviour and expected failure tests, but I am lazy ;-). I think that's okay. Many, many new features and bug fixes come with tests. I think that we do not have _few_ tests. At least not comparing to other projects (especially commercial ones...). Ciao, Dscho - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html