karma-firefox-launcher

WebJar for karma-firefox-launcher

License

License

MIT
GroupId

GroupId

org.webjars.npm
ArtifactId

ArtifactId

karma-firefox-launcher
Last Version

Last Version

1.3.0
Release Date

Release Date

Type

Type

jar
Description

Description

karma-firefox-launcher
WebJar for karma-firefox-launcher
Project URL

Project URL

https://www.webjars.org
Source Code Management

Source Code Management

https://github.com/karma-runner/karma-firefox-launcher

Download karma-firefox-launcher

How to add to project

<!-- https://jarcasting.com/artifacts/org.webjars.npm/karma-firefox-launcher/ -->
<dependency>
    <groupId>org.webjars.npm</groupId>
    <artifactId>karma-firefox-launcher</artifactId>
    <version>1.3.0</version>
</dependency>
// https://jarcasting.com/artifacts/org.webjars.npm/karma-firefox-launcher/
implementation 'org.webjars.npm:karma-firefox-launcher:1.3.0'
// https://jarcasting.com/artifacts/org.webjars.npm/karma-firefox-launcher/
implementation ("org.webjars.npm:karma-firefox-launcher:1.3.0")
'org.webjars.npm:karma-firefox-launcher:jar:1.3.0'
<dependency org="org.webjars.npm" name="karma-firefox-launcher" rev="1.3.0">
  <artifact name="karma-firefox-launcher" type="jar" />
</dependency>
@Grapes(
@Grab(group='org.webjars.npm', module='karma-firefox-launcher', version='1.3.0')
)
libraryDependencies += "org.webjars.npm" % "karma-firefox-launcher" % "1.3.0"
[org.webjars.npm/karma-firefox-launcher "1.3.0"]

Dependencies

compile (1)

Group / Artifact Type Version
org.webjars.npm : is-wsl jar [2.1.0,3)

Project Modules

There are no modules declared in this project.

karma-firefox-launcher

js-standard-style npm version npm downloads semantic-release

Build Status Dependency Status devDependency Status

Launcher for Mozilla Firefox.

Installation

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

You can simple do it by:

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

Configuration

// karma.conf.js
module.exports = function(config) {
  config.set({
    browsers: ['Firefox', 'FirefoxDeveloper', 'FirefoxAurora', 'FirefoxNightly'],
  })
}

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

karma 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:

browsers: ['Firefox68', 'Firefox78'],

customLaunchers: {
    Firefox68: {
        base: 'Firefox',
        name: 'Firefox68',
        command: '<path to FF68>/firefox.exe'
    },
    Firefox78: {
        base: 'Firefox',
        name: 'Firefox78',
        command: '<path to FF78>/firefox.exe'
    }
}

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:

browsers: ['FirefoxAutoAllowGUM'],

customLaunchers: {
    FirefoxAutoAllowGUM: {
        base: 'Firefox',
        prefs: {
            'media.navigator.permission.disabled': true
        }
    }
}

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:

browsers: ['FirefoxWithMyExtension'],

customLaunchers: {
    FirefoxWithMyExtension: {
        base: 'Firefox',
        extensions: [
          path.resolve(__dirname, 'helpers/extensions/[email protected]'),
          path.resolve(__dirname, 'helpers/extensions/[email protected]')
        ]
    }
}

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:

<?xml version="1.0" encoding="utf-8"?>
   <RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:em="http://www.mozilla.org/2004/em-rdf#">
  <Description about="urn:mozilla:install-manifest">
    <em:id>myCustomExt@suchandsuch</em:id>
    <em:version>1.0</em:version>
    <em:type>2</em:type>
    <em:bootstrap>true</em:bootstrap>
    <em:unpack>false</em:unpack>

    [...]
  </Description>
</RDF>

Then you should name your extension [email protected].


For more information on Karma see the homepage.

org.webjars.npm

Karma

The Spectacular Test Runner for JavaScript.

Versions

Version
1.3.0
0.1.7
0.1.6