karma-browserstack-browserslist-launchers
Automatic BrowserStack launchers based on browserslist config.
Last updated 8 months ago by bashmish .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install karma-browserstack-browserslist-launchers 
SYNC missed versions from official npm registry.

karma-browserstack-browserslist-launchers

Integrates with karma-browserstack-launcher and automatically configures karma browsers and launchers for them based on your browserslist config.

Configuration

You need both karma-browserstack-browserslist-launchers and karma-browserstack-launcher to be installed.

  • .browserslistrc (just an example)

    last 2 Chrome major versions
    last 2 Firefox major versions
    last 2 Safari major versions
    last 2 Edge major versions
    
  • karma.conf.js

    module.exports = (config) => {
      // ...
      
      // add to frameworks
      config.frameworks = ['browserStackBrowserslistLaunchers'];
    
      // configure karma-browserstack-launcher
      config.browserStack = {
        username: process.env.BROWSERSTACK_USERNAME,
        accessKey: process.env.BROWSERSTACK_ACCESS_KEY,
        project: 'my-project',
      };
    
      // ...
    };
    

Latest browser versions

Your browserslist config is always processed using browserslist NPM package which contains data about versions of different browsers. To stay up-to-date and have latest versions of everything it is recommended to depend on it directly (npm install browserslist --save-dev) and update it from time to time.

Be aware though that BrowserStack itself might not have a certain version of a browser available.

Processing of capabilities

After matching BrowserStack capabilities with browserslist config there are too many available capabilities, because each browser version might be available on many OS, e.g. Chrome 76 can be tested on Windows 7, 8, 10 and multiple version of macOS. This is just too much to run and is not needed in the majority of cases. Therefore by default the capabilities are filtered and each unique browser version will be tested only on one OS.

If you don't like the default strategy you can hook into the process and apply a different filtering like this:

  • karma.conf.js

    module.exports = (config) => {
      // ...
    
      config.browserStackBrowserslistLaunchers = {
        processCapabilities: (capabilities) => {
          // you can filter the array here
          return capabilities.filter(/* filter */);
        },
      };
    
      // ...
    };
    

Current Tags

  • 0.1.0                                ...           latest (8 months ago)

1 Versions

  • 0.1.0                                ...           8 months ago
Maintainers (1)
Downloads
Today 0
This Week 1
This Month 1
Last Day 1
Last Week 0
Last Month 1
Dependencies (2)
Dev Dependencies (0)
None
Dependents (0)
None

Copyright 2014 - 2017 © taobao.org |