Commit Graph

11 Commits

Author SHA1 Message Date
Brian Tiger Chow
4678dea045 tests(sharness) attempt to execute sharness tests on ipfs2
@jbenet @chriscool

(not to be merged into master) This is a hack to run sharness tests on
th ipfs2 binary. Instead of compiling cmd/ipfs, it compiles cmd/ipfs2
and copies this into test/bin/ipfs.

I thought this would be enough to pass the `basic-commands` test, but
it's not.

Although the output is fairly similar, the `ipfs version` test fails.

```
test (feat/test2) λ. diff version1 version2
1c1
< ipfs version 0.1.7
---
> ipfs version 0.1.5
```

I'm not very experienced with `sh` scripting, so perhaps I'm missing a
key ingredient or maybe misunderstanding the the tests are meant to
work.

Would like to get input on this.

Thanks, @maybebtc
2014-11-16 03:20:10 -08:00
Juan Batiz-Benet
842de46ccf test: moved installed things into own dirs
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.
2014-11-08 20:12:02 -08:00
Juan Batiz-Benet
5680c112ef test: install random from vendored code 2014-11-08 18:49:28 -08:00
Christian Couder
2b5f1b2d8c Install sharness in a 'sharness' directory
It is cleaner if sharness is installed in its own
directory.
2014-11-08 02:44:03 +01:00
Juan Batiz-Benet
04efbb9a55 test: install random locally for travis. 2014-11-07 17:24:13 -08:00
Juan Batiz-Benet
7ab38696f6 travis: fix install random error 2014-11-07 15:24:31 -08:00
Juan Batiz-Benet
7e14f1737d test/: build own ipfs tool to test
The tests were using the globally installed ipfs.
This commit changes it to build + use its own ipfs binary.
2014-11-07 15:16:29 -08:00
Juan Batiz-Benet
37279d55ca install go-random 2014-11-07 14:54:58 -08:00
Juan Batiz-Benet
9535cb5802 install sharness 2014-11-07 14:53:55 -08:00
Christian Couder
07bd18b53d Display which Makefile target is launched
License: MIT
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
2014-10-26 10:10:22 +01:00
Christian Couder
aeb019f2b8 Add test/Makefile to run the test scripts
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
2014-10-25 14:12:27 +02:00