Re: [PATCH v3 3/9] tree: increase test coverage for tree.c

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Heather Lapointe via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes:
> +	setup_git_directory();
> +	repo = the_repository;
> +	assert(repo);
> +
> +	parse_pathspec(&pathspec, 0,
> +		       PATHSPEC_PREFER_FULL,
> +		       "", argv);

Here, the repository is hardcoded to be "the_repository", and the C 
code allows the pathspec to be varied but the shell test code always 
specifies "." as the pathspec. Given that one of the main points of 
this series is the repo varying, could the repo be taken in as a CLI 
argument? The pathspec can be left variable, but if it's not going to 
change, you might as well hardcode it in the C code. 

The existing test cases of a basic one and a recursing one is good, but 
it would be good also to have one where the repo being passed into the 
function is not the repo whose directory we're currently executing in 
(that is, different to the_repository). That way we can test that the 
function works for arbitrary repositories.

 



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux