Skip to content
Branch: master
Find file History
zlatin and wbamberg convert chrome. to browser. Issue #165 #166 (#262)
* convert chrome. to browser. Issue #165

* fix browser-polyfill

* convert chrome.* to browser.* (#166)

* convert chrome.* to browser.*

* change chrome to browser

* change the callback-style to promise-style

* change the callback-style to promise-style
Latest commit f369ddc Sep 11, 2017

README.md

Mocha client tests for WebExtensions

Introduction

This example shows two methods of testing a WebExtension:

  • Running tests from within the addon
  • Running tests from the commandline using Karma

See https://github.com/Standard8/example-webextension for a more complete example of WebExtension test configuration.

Install Dependencies:

  npm install

To run tests from within the addon:

  cd addon
  npm install

Testing within the Addon

This gives you the possibility to run client tests inside the addon with the mocha UI. If you don't want to use the mocha UI, you can install WebConsole-reporter.

Run with web-ext cli

Just run npm run web-ext (will work with FF dev edition), if you have error with web-ext cli please add path for FF binary file with --firefox-binary /path/to/firefox-bin (web-ext docs).

When the addon starts, click on the mocha icon in your browser bar to run the tests:

addon screenshot

This will test ./addon/background.js with ./addon/tests/lib/background-messaging.test.js.

Testing from the Commandline

This uses Karma to run tests from the commandline. Just type npm test to test ./addon/background.js with ./tests/lib/background.test.js.

Debug Mode

Use npm run test:debug to run Karma in watch mode. Whenever you modify a Javascript file, the tests will automatically rerun.

You can install karma-notification-reporter to display test results in a desktop notification. You'll need to add --reporters=dots,notification to the test:debug command line of package.json to enable it.

You can’t perform that action at this time.