-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Sharness tests #412
Comments
@diasdavid yeah I started to take a look at that during the Lisbon workshop, but there were a lot of problems, startin with |
I was more thinking in the lines of using go-ipfs cli to point to js-ipfs http api (ipfs --api='') so that we can tell that both behave the same way, avoiding to have to write the entire CLI. |
@chriscool any update about this? |
@diasdavid I had a vacation and I am at the LinuxCon in Toronto now until next Monday. |
@chriscool how are things? Can we look into this again? jsipfs is now interopable with go-ipfs (so we can have tests that use both at the same time) and the CLI is getting the same features + interface :) |
@diasdavid great that it's now interoperable! Could we discuss it and try to do something tomorrow morning at around 9 am CEST time or are you available now? |
@chriscool I'm currently in NYC, so 9am CEST would be 4am for me. Can we make it in your afternoon? |
@diasdavid then I think 9pm CEST is better for me. That would be 4pm for you. |
@diasdavid actually 9pm CEST is not possible today for me. I forgot that I had planned to meet friends. But it's possible tomorrow (Thursday September 15). Would that work for you? |
@chriscool Thank you for handling this, I see you have opened the PR's, let's follow on those ones: |
In order to improve the quality and robustness of js-ipfs, it is pretty important to reuse the SHarness testing infrastructure against the js-ipfs http-api.
@chriscool could you help us with that? I think the best first step is to have the go-ipfs cli point at the js-ipfs http-api and test the endpoints that js-ipfs already implements (i.e: object, block, bitswap, add, cat, get). We can do that by pulling
go-ipfs
as a devdependency and run it in CIThe text was updated successfully, but these errors were encountered: