Re: omitted test scripts?
- From
Junio C Hamano <junkio@cox.net>
- Date
- Sep 19, 2005, 16:19 UTC
- Message-ID
- <7v1x3lrpxi.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <432EDE3F.7070407@citi.umich.edu>
Chuck Lever <cel@citi.umich.edu> writes:
> i noticed while testing the new cache API that there are no tests under > t/ for git-merge-index.
In the past, when I did any major butchering of existing code or made nontrivial additions, I wrote test scripts to cover what should happen (and what to be preserved) first to make sure the changes or additions would not introduce regression. I think we have been reasonably successful (Daniel could fill us in with experiences with read-tree tests).
I have been expecting people to follow suit, without explicitly asking them to do, so when I took over the project. Further I got sloppy when accepting any sizable patches. Sorry about that.
> there is also no test script that covers the prune_cache() function in > ls-files.c.
That's one of the item on the TODO list and patches to extend test coverage are always welcomed.