Recreate Test Suite

[lidel]

In legacy SDK we had a comprehensive test suite that was run via jpm test

WebExtensions use web-ext, but it does not provide test runner yet.
There is a related, open issue at mozilla/web-ext#5.

This issue is blocked until WebExtension test runner is implemented upstream, or a custom npm tests command is implemented locally AND we reach 80%+ test coverage

(updated 2017-12-02)

• npm test runs test suite with browser stub
• think about Browser detection (we have Firefox/Chrome/Brave specific workarounds in codebase)
• TODO: go over tests in legacy-sdk branch and add missing unit tests here
• Research if we are able to run integration tests against real browsers with assertions that check browser UI
  • https://firefox-puppeteer.readthedocs.io:

    Firefox Puppeteer provides a library to manipulate each visual section of Firefox’s browser UI. For example, there are different libraries for the tab bar, the navigation bar, etc.

[lidel]

Ok, seems that mozilla suggests mocha, karma with unit tests where WebExtensions stubbed by the sinon-chrome package and functional ones handled via geckodriver:

• https://github.com/mozilla/example-addon-repo/blob/b7f75fd8cbc539eb318be9cf79ab371e985b696e/docs/UnitTests.md
• https://github.com/mozilla/example-addon-repo/blob/34d82b5f1b3a03654ff643ad8b5acb8dca5b8b55/docs/Functional.md

[cvan]

This might be worth giving a shot using testcafe. Let me know your thoughts. If there's interest, I'd be glad to help.

[lidel]

We may want to revisit tests in Q4 with:

A command line tool (inspired by tape) can be used to test Firefox web extensions.
It starts Firefox in headless mode using Web Driver and install temporary test web extensions that are assumed to produce TAP output. You can use libdweb experimental test API which is API compatible with tape for writing tests.

– https://github.com/gozala/tape-ext