Skip to content

Latest commit

 

History

History
159 lines (115 loc) · 5.9 KB

README.md

File metadata and controls

159 lines (115 loc) · 5.9 KB

No Maintenance Intended

DalekJS is not maintained any longer 😢

We recommend TestCafé for your automated browser testing needs.


dalek-driver-sauce

DalekJS driver bindings for Sauce Labs integration

Build Status Build Status Dependency Status devDependency Status NPM version Coverage unstable Stories in Ready Bitdeli Badge Built with Grunt

NPM NPM

Ressources

API Docs - Trello - Code coverage - Code complexity - Contributing - User Docs - Homepage - Twitter

Docs

This module is a driver plugin for DalekJS. It connects Daleks testsuite with the remote testing environment of Sauce Labs.

The driver can be installed with the following command:

$ npm install dalek-driver-sauce --save-dev

You can use the driver by adding a config option to the your Dalekfile

"driver": ["sauce"]

Or you can tell Dalek that it should run your tests via sauces service via the command line:

$ dalek mytest.js -d sauce

In order to run your tests within the Sauce Labs infrastructure, you must add your sauce username & key to your dalek configuration. Those two parameters must be set in order to get this driver up & running. You can specifiy them within your Dalekfile like so:

"driver.sauce": {
  "user": "dalekjs",
  "key": "aaaaaa-1234-567a-1abc-1br6d9f68689"
}

It is also possible to specify a set of other extra saucy parameters like name & tags:

"driver.sauce": {
  "user": "dalekjs",
  "key": "aaaaaa-1234-567a-1abc-1br6d9f68689",
  "name": "Guineapig",
  "tags": ["dalek", "testproject"]
}

If you would like to have a more control over the browser/OS combinations that are available, you are able to configure you custom combinations:

"browsers": [{
  "chrome": {
    "platform": "OS X 10.6",
    "actAs": "chrome",
    "version": 27
  },
  "chromeWin": {
    "platform": "Windows 7",
    "actAs": "chrome",
    "version": 27
  },
  "chromeLinux": {
    "platform": "Linux",
    "actAs": "chrome",
    "version": 26
  }

You can then call your custom browsers like so:

$ dalek mytest.js -d sauce -b chrome,chromeWin,chromeLinux

or you can define them in your Dalekfile:

"browser": ["chrome", "chromeWin", "chromeLinux"]

A list of all available browser/OS combinations, can be found here.

Help Is Just A Click Away

#dalekjs on FreeNode.net IRC

Join the #daleksjs channel on FreeNode.net to ask questions and get help.

Get announcements for new releases, share your projects and ideas that are using DalekJS, and join in open-ended discussion that does not fit in to the Github issues list or StackOverflow Q&A.

For help with syntax, specific questions on how to implement a feature using DalekJS, and other Q&A items, use StackOverflow.

Ask questions about using DalekJS in specific scenarios, with specific features. For example, help with syntax, understanding how a feature works and how to override that feature, browser specific problems and so on.

Questions on StackOverflow often turn in to blog posts or issues.

Report issues with DalekJS, submit pull requests to fix problems, or to create summarized and documented feature requests (preferably with pull requests that implement the feature).

Please don't ask questions or seek help in the issues list. There are other, better channels for seeking assistance, like StackOverflow and the Google Groups mailing list.

DalekJS

Legal FooBar (MIT License)

Copyright (c) 2013 Sebastian Golasch

Distributed under MIT license