Created
January 27, 2016 21:04
-
-
Save dcypherthis/ba5de10ee60b0a030012 to your computer and use it in GitHub Desktop.
wdio-cucumber with babel
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
exports.config = { | |
// | |
// ================== | |
// Specify Test Files | |
// ================== | |
// Define which test specs should run. The pattern is relative to the directory | |
// from which `wdio` was called. Notice that, if you are calling `wdio` from an | |
// NPM script (see https://docs.npmjs.com/cli/run-script) then the current working | |
// directory is where your package.json resides, so `wdio` will be called from there. | |
// | |
specs: [ | |
'./test/features/**/*.feature' | |
], | |
// Patterns to exclude. | |
exclude: [ | |
// 'path/to/excluded/files' | |
], | |
// | |
// ============ | |
// Capabilities | |
// ============ | |
// Define your capabilities here. WebdriverIO can run multiple capabilties at the same | |
// time. Depending on the number of capabilities, WebdriverIO launches several test | |
// sessions. Within your capabilities you can overwrite the spec and exclude option in | |
// order to group specific specs to a specific capability. | |
// | |
// If you have trouble getting all important capabilities together, check out the | |
// Sauce Labs platform configurator - a great tool to configure your capabilities: | |
// https://docs.saucelabs.com/reference/platforms-configurator | |
// | |
capabilities: [{ | |
browserName: 'firefox'} | |
// { | |
// browserName: 'chrome'} | |
//{ | |
// browserName: 'phantomjs'} | |
//{ | |
// browserName: 'safari'} | |
], | |
// | |
// =================== | |
// Test Configurations | |
// =================== | |
// Define all options that are relevant for the WebdriverIO instance here | |
// | |
// Level of logging verbosity: silent | verbose | command | data | result | error | |
logLevel: 'silent', | |
// | |
// Enables colors for log output. | |
coloredLogs: true, | |
// | |
// Saves a screenshot to a given path if a command fails. | |
screenshotPath: './test/errorShots/', | |
// | |
// Set a base URL in order to shorten url command calls. If your url parameter starts | |
// with "/", the base url gets prepended. | |
baseUrl: 'https://app.e2ma.net/app2/login/', | |
// | |
// Default timeout for all waitForXXX commands. | |
waitforTimeout: 10000, | |
// | |
// Initialize the browser instance with a WebdriverIO plugin. The object should have the | |
// plugin name as key and the desired plugin options as property. Make sure you have | |
// the plugin installed before running any tests. The following plugins are currently | |
// available: | |
// WebdriverCSS: https://github.com/webdriverio/webdrivercss | |
// WebdriverRTC: https://github.com/webdriverio/webdriverrtc | |
// Browserevent: https://github.com/webdriverio/browserevent | |
// plugins: { | |
// webdrivercss: { | |
// screenshotRoot: 'my-shots', | |
// failedComparisonsRoot: 'diffs', | |
// misMatchTolerance: 0.05, | |
// screenWidth: [320,480,640,1024] | |
// }, | |
// webdriverrtc: {}, | |
// browserevent: {} | |
// }, | |
// | |
// Framework you want to run your specs with. | |
// The following are supported: mocha, jasmine and cucumber | |
// see also: http://webdriver.io/guide/testrunner/frameworks.html | |
// | |
// Make sure you have the node package for the specific framework installed before running | |
// any tests. If not please install the following package: | |
// Mocha: `$ npm install mocha` | |
// Jasmine: `$ npm install jasmine` | |
// Cucumber: `$ npm install cucumber` | |
framework: 'cucumber', | |
// | |
// Test reporter for stdout. | |
// The following are supported: dot (default), spec and xunit | |
// see also: http://webdriver.io/guide/testrunner/reporters.html | |
reporter: 'spec', | |
// | |
// If you are using Cucumber you need to specify where your step definitions are located. | |
cucumberOpts: { | |
require: ['./test/support/stepDefinitions/**/*.js'], | |
// Enable this config to treat undefined definitions as warnings. | |
ignoreUndefinedDefinitions: false, | |
// run only certain scenarios annotated by tags | |
// tags: ['foo', 'bar'] | |
}, | |
// | |
// ===== | |
// Hooks | |
// ===== | |
// Run functions before or after the test. If one of them returns with a promise, WebdriverIO | |
// will wait until that promise got resolved to continue. | |
// | |
// Gets executed before all workers get launched. | |
onPrepare: function() { | |
// do something | |
}, | |
// | |
// Gets executed before test execution begins. At this point you will have access to all global | |
// variables like `browser`. It is the perfect place to define custom commands. | |
before: function() { | |
require('babel-register')({ | |
blacklist: [ | |
'regenerator' | |
] | |
}); | |
setTimeout(() => { | |
console.log('we get here too') | |
}, 2000); | |
var chai = require('chai'); | |
var chaiAsPromised = require('chai-as-promised'); | |
chai.use(chaiAsPromised); | |
chai.Should(); | |
chaiAsPromised.transferPromiseness = browser.transferPromiseness; | |
}, | |
// | |
// Gets executed after all tests are done. You still have access to all global variables from | |
// the test. | |
after: function(failures, pid) { | |
// do something | |
}, | |
// | |
// Gets executed after all workers got shut down and the process is about to exit. It is not | |
// possible to defer the end of the process using a promise. | |
onComplete: function() { | |
// do something | |
} | |
}; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment