- 09 Nov, 2014 2 commits
-
-
Juan Batiz-Benet authored
I moved installed things into own dirs bin and lib. @chriscool sorry to move things around again, the top level test dir was getting a bit clutterd.
-
Juan Batiz-Benet authored
-
- 08 Nov, 2014 2 commits
-
-
Christian Couder authored
It is cleaner if sharness is installed in its own directory.
-
Juan Batiz-Benet authored
-
- 07 Nov, 2014 4 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
The tests were using the globally installed ipfs. This commit changes it to build + use its own ipfs binary.
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
- 26 Oct, 2014 1 commit
-
-
Christian Couder authored
License: MIT Signed-off-by:
Christian Couder <chriscool@tuxfamily.org>
-
- 25 Oct, 2014 1 commit
-
-
Christian Couder authored
You can use it like this to launch all the test scripts in order: $ cd test $ make rm -r test-results *** t0010-basic-commands.sh *** ok 1 - current dir is writable ok 2 - ipfs version succeeds ok 3 - ipfs version output looks good ok 4 - ipfs help succeeds ok 5 - ipfs help output looks good # passed all 5 test(s) 1..5 ./test-aggregate-results.sh fixed 0 success 5 failed 0 broken 0 total 5 Or you can just run one test like this: $ make t0010-basic-commands.sh *** t0010-basic-commands.sh *** ok 1 - current dir is writable ok 2 - ipfs version succeeds ok 3 - ipfs version output looks good ok 4 - ipfs help succeeds ok 5 - ipfs help output looks good # passed all 5 test(s) 1..5
-