~This doesn't check that the shellouts work (because I wasn't sure how to
do that*) -- but at least it asserts he right info formats, and checks
repo_path() and packages_path().~ (This is only some rather shallow unit tests; integration tests for stable fetch are tracked in #28.)
The tag-related "complete" info cases are there for completeness' sake
more than functional implications -- as the checkout isn't tested, they
have little effect.
*how to do that using only pony -- I suppose we could resort to setting up some per-test $PATH pointing to shell script stubs for git, etc
@mfelsche I'm merging this, hope you don't mind. Optimistically assuming to have answered your question -- happy to revisit this if it's not the case. :)
~This doesn't check that the shellouts work (because I wasn't sure how to do that*) -- but at least it asserts he right info formats, and checks repo_path() and packages_path().~ (This is only some rather shallow unit tests; integration tests for
stable fetch
are tracked in #28.)The tag-related "complete" info cases are there for completeness' sake more than functional implications -- as the checkout isn't tested, they have little effect.
*how to do that using only pony -- I suppose we could resort to setting up some per-test
$PATH
pointing to shell script stubs forgit
, etc