Sharness is abstracted into own project that can run for either go-ipfs or js-ipfs

[victorb]

No description provided.

[victorb]

@chriscool I'm in the progress of setting up everything for this working group. This would be the issue for working on extracting sharness. Once this repository is public, we can close ipfs/notes#265 and redirect to here.

Will fill out my ideas on how to make this possible in the description above during the day.

[chriscool]

@victorbjelkholm there is now this repo:

https://github.com/chriscool/ipfs-sharness-tests

After cloning this repo you have to drop some binaries in the bin/ directory, and then you can run make and it will run sharness tests against the binaries in the bin/ directory.

Of course the most important binary should be called "ipfs" and the sharness tests are focused on testing this binary. This binary should be the result of a build of go-ipfs, js-ipfs or maybe another ipfs implementation.

Other binaries are:

• go-sleep
• go-timeout
• hang-fds
• iptb
• ma-pipe-unidir
• multihash
• pollEndpoint
• random
• random-files

There are rules in the go-ipfs makefiles to build these binaries. Maybe these rules should be part of the https://github.com/chriscool/ipfs-sharness-tests repo, so that only the "ipfs" binary has to be provided.

[chriscool]

Of course we can move this repo to https://github.com/ipfs/ but I am not sure I have the rights to do that.