Headless Chrome Tests

[aphelionz]

Description

Branching from partway through https://github.com/orbitdb/ipfs-log/pull/186, this work continues the browser testing. I like the paradigm overall, using mocha-chrome-headless to run the tests. As the PR stands, it is a proof of concept using CircleCI to run the tests.

Resolves #41

TODO

Fix the replication tests

• [ ] Merge master in. As it stands right now, the js-ipfs upgrade from0.31 to 0.33 (or the js-ipfs-repo upgrade) will break the builds, particularly the node.js replication tests.
• [ ] Re-enable the replication tests in the browser.

Scripts

• npm run build:tests: Builds test/browser/bundle.js and test/browser/bundle.js.map
• npm run test:browser: Runs npm test build and then tests test/browser/index.html with `mocha-headless-chrome

Deps

New dependencies:

• orbit-db-identity-provider: updated to ^0.0.3

New dev dependencies:

• mocha-headless-chrome: ~2.0.1
• is-node: ^1.0.2

[haadcode]

@aphelionz thanks for the PR and continuing the previous efforts! 👍

I spend some time today to look at the failing replication tests, but can't figure out what's going on. The short is, I'm seeing weird errors (not seen before) from ipfs/libp2p as I tested through the various config options. The same observations though, the peers can't connect.

I'd be happy to skip the replications tests in the browser for now in order to move this PR ahead. We'll need to solve the replication/connectivity problems for orbitdb browser tests too, so let's do that at the same time.

I rebased the branch on master and made a small change to make it explicit that we're skipping the replications tests (as opposed to not including them). Perhaps we should add a "if (isNode)" check to those tests to not skip them when running in nodejs?

[aphelionz]

@haadcode Just confirmed, tests passing with this merged into master. Review one last time and I'm ready to merge.

[haadcode]

Thanks for the PR @aphelionz! 👍