karma-firefox-launcher

Launcher for Mozilla Firefox.

karma-firefox-launcher is deprecated and is not accepting new features or general bug fixes.

See deprecation notice for karma.

Web Test Runner, jasmine-browser-runner, and playwright-test provide browser-based unit testing solutions which can be used as a direct alternative.

Installation

The easiest way is to keep karma-firefox-launcher as a devDependency in your package.json.

You can simple do it by:

1npm install karma-firefox-launcher --save-dev

Configuration

1// karma.conf.js
2module.exports = function (config) {
3  config.set({
4    plugins: [require("karma-firefox-launcher")],
5    browsers: [
6      "Firefox",
7      "FirefoxDeveloper",
8      "FirefoxAurora",
9      "FirefoxNightly",
10    ],
11  });
12};

You can pass list of browsers as a CLI argument too:

1karma start --browsers Firefox,Chrome

To run Firefox in headless mode, append Headless to the version name, e.g. FirefoxHeadless, FirefoxNightlyHeadless.

Environment variables

You can specify the location of the Firefox executable using the following environment variables:

• FIREFOX_BIN (for browser Firefox or FirefoxHeadless)
• FIREFOX_DEVELOPER_BIN (for browser FirefoxDeveloper or FirefoxDeveloperHeadless)
• FIREFOX_AURORA_BIN (for browser FirefoxAurora or FirefoxAuroraHeadless)
• FIREFOX_NIGHTLY_BIN (for browser FirefoxNightly or FirefoxNightlyHeadless)

Custom Firefox location

In addition to Environment variables you can specify location of the Firefox executable in a custom launcher:

1browsers: ['Firefox68', 'Firefox78'],
2
3customLaunchers: {
4    Firefox68: {
5        base: 'Firefox',
6        name: 'Firefox68',
7        command: '<path to FF68>/firefox.exe'
8    },
9    Firefox78: {
10        base: 'Firefox',
11        name: 'Firefox78',
12        command: '<path to FF78>/firefox.exe'
13    }
14}

Custom Preferences

To configure preferences for the Firefox instance that is loaded, you can specify a custom launcher in your Karma config with the preferences under the prefs key:

1browsers: ['FirefoxAutoAllowGUM'],
2
3customLaunchers: {
4    FirefoxAutoAllowGUM: {
5        base: 'Firefox',
6        prefs: {
7            'media.navigator.permission.disabled': true
8        }
9    }
10}

Loading Firefox Extensions

If you have extensions that you want loaded into the browser on startup, you can specify the full path to each extension in the extensions key:

1browsers: ['FirefoxWithMyExtension'],
2
3customLaunchers: {
4    FirefoxWithMyExtension: {
5        base: 'Firefox',
6        extensions: [
7          path.resolve(__dirname, 'helpers/extensions/myCustomExt@suchandsuch.xpi'),
8          path.resolve(__dirname, 'helpers/extensions/myOtherExt@soandso.xpi')
9        ]
10    }
11}

Please note: the extension name must exactly match the 'id' of the extension. You can discover the 'id' of your extension by extracting the .xpi (i.e. unzip XXX.xpi) and opening the install.RDF file with a text editor, then look for the em:id tag under the Description tag. If your extension manifest looks something like this:

1<?xml version="1.0" encoding="utf-8"?>
2   <RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:em="http://www.mozilla.org/2004/em-rdf#">
3  <Description about="urn:mozilla:install-manifest">
4    <em:id>myCustomExt@suchandsuch</em:id>
5    <em:version>1.0</em:version>
6    <em:type>2</em:type>
7    <em:bootstrap>true</em:bootstrap>
8    <em:unpack>false</em:unpack>
9
10    [...]
11  </Description>
12</RDF>

Then you should name your extension myCustomExt@suchandsuch.xpi.

---

For more information on Karma see the homepage.