forked from insideout10/wordlift-plugin
-
Notifications
You must be signed in to change notification settings - Fork 0
/
wdio.conf.js
289 lines (267 loc) · 11.1 KB
/
wdio.conf.js
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
var config = {
//
// =================
// Service Providers
// =================
// WebdriverIO supports Sauce Labs, Browserstack, and Testing Bot (other
// cloud providers should work too though). These services define specific
// user and key (or access key) values you need to put in here in order to
// connect to these services. user: process.env.SAUCE_USERNAME, key:
// process.env.SAUCE_ACCESS_KEY,
// `sauceConnect` must be false when running in Travis-CI, since Travis-CI
// is providing SauceConnect. Remember: !undefined === true For a list of
// Travis provided environment variables:
// https://docs.travis-ci.com/user/environment-variables/#Default-Environment-Variables
sauceConnect: ! process.env.CI,
//
// ==================
// 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: [
'./tests/e2e/tests/**/*Spec.js'
],
// Patterns to exclude.
exclude: [
// 'path/to/excluded/files'
],
//
// ============
// Capabilities
// ============
// Define your capabilities here. WebdriverIO can run multiple capabilities
// 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 options in order to group specific specs
// to a specific capability. First, you can define how many instances
// should be started at the same time. Let's say you have 3 different
// capabilities (Chrome, Firefox, and Safari) and you have set maxInstances
// to 1; wdio will spawn 3 processes. Therefore, if you have 10 spec files
// and you set maxInstances to 10, all spec files will get tested at the
// same time and 30 processes will get spawned. The property handles how
// many capabilities from the same test should run tests.
maxInstances: 10,
//
// 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: [
// // maxInstances can get overwritten per capability. So if you have
// an in-house Selenium // grid with only 5 firefox instances available
// you can make sure that not more than // 5 instances get started at a
// time. maxInstances: 5, name: 'WordLift Cross-Browsing Tests (#' +
// process.env.TRAVIS_BUILD_NUMBER + ')', 'tunnel-identifier':
// process.env.TRAVIS_JOB_NUMBER, build:
// process.env.TRAVIS_BUILD_NUMBER,
// If using Open Sauce (https://saucelabs.com/opensauce/),
// capabilities must be tagged as "public" for the jobs's status
// to update (failed/passed). If omitted on Open Sauce, the job's
// status will only be marked "Finished." This property can be
// be omitted for commercial (private) Sauce Labs accounts.
// Also see
// https://support.saucelabs.com/customer/portal/articles/2005331-why-do-my-tests-say-%22finished%22-instead-of-%22passed%22-or-%22failed%22-how-do-i-set-the-status-
// 'public': true,
// See http://webdriver.io/guide/usage/multiremote.html
//
// See:
// * https://wiki.saucelabs.com/display/DOCS/Platform+Configurator#/
// * https://github.com/SeleniumHQ/selenium/wiki/DesiredCapabilities
// *
// https://github.com/webdriverio/webdriverio/blob/master/examples/cloudservices/webdriverio.saucelabs.js
{
browserName: 'firefox'
}
],
//
// ===================
// Test Configurations
// ===================
// Define all options that are relevant for the WebdriverIO instance here
//
// By default WebdriverIO commands are executed in a synchronous way using
// the wdio-sync package. If you still want to run your tests in an async
// way e.g. using promises you can set the sync option to false.
sync: true,
//
// Level of logging verbosity: silent | verbose | command | data | result |
// error
logLevel: 'error',
//
// Enables colors for log output.
coloredLogs: true,
//
// Saves a screenshot to a given path if a command fails.
screenshotPath: './errorShots/',
//
// Set a base URL in order to shorten url command calls. If your url
// parameter starts with "/", then the base url gets prepended.
baseUrl: 'http://wordpress.localhost',
//
// Default timeout for all waitFor* commands.
waitforTimeout: 10000,
//
// Default timeout in milliseconds for request
// if Selenium Grid doesn't send response
connectionRetryTimeout: 90000,
//
// Default request retries count
connectionRetryCount: 3,
//
// Initialize the browser instance with a WebdriverIO plugin. The object
// should have the plugin name as key and the desired plugin options as
// properties. 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: {} }, Test runner services Services
// take over a specific job you don't want to take care of. They enhance
// your test setup with almost no effort. Unlike plugins, they don't add
// new commands. Instead, they hook themselves up into the test process.
services: [ 'firefox-profile', 'selenium-standalone' ],
firefoxProfile: {
'security.insecure_field_warning.contextual.enabled': false
},
//
// 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 wdio adapter package for the specific framework
// installed before running any tests.
framework: 'jasmine',
//
// Test reporter for stdout.
// The only one supported by default is 'dot'
// see also: http://webdriver.io/guide/testrunner/reporters.html
reporters: [ 'dot' ],
//
// Options to be passed to Jasmine.
jasmineNodeOpts: {
//
// Jasmine default timeout
defaultTimeoutInterval: 60000,
//
// The Jasmine framework allows interception of each assertion in order
// to log the state of the application or website depending on the
// result. For example, it is pretty handy to take a screenshot every
// time an assertion fails.
expectationResultHandler: function( passed, assertion ) {
// do something
}
},
/**
* Gets executed just before initialising the webdriver session and test
* framework. It allows you to manipulate configurations depending on the
* capability or spec.
* @param {Object} config wdio configuration object
* @param {Array.<Object>} capabilities list of capabilities details
* @param {Array.<String>} specs List of spec file paths that are to be run
*/
beforeSession: function( config, capabilities, specs ) {
// Copy the baseUrl from the browser's capabilities settings.
config.baseUrl = capabilities.baseUrl;
},
// //
// // =====
// // Hooks
// // =====
// // WebdriverIO provides several hooks you can use to interfere with the
// // test process in order to enhance it and to build services around it.
// You // can either apply a single function or an array of methods to it. If
// one // of them returns with a promise, WebdriverIO will wait until that
// promise // got resolved to continue. Gets executed once before all workers
// get // launched. `capabilities` here contain the array of `capabilities`. //
// onPrepare: function (config, capabilities) { }, // Gets executed before //
// test execution begins. At this point you can access all global // variables,
// such as `browser`. It is the perfect place to define custom // commands.
before: function( capabilities, specs ) {
// Set the browser's `baseUrl` from the `capabilities` 's `baseUrl` in
// order to have each browser go to a different WordPress setup.
if ( capabilities.baseUrl ) {
browser.options.baseUrl = capabilities.baseUrl;
}
browser.timeouts( 'implicit', 10000 );
}
//
// Hook that gets executed before the suite starts
// beforeSuite: function (suite) {
// },
//
// Hook that gets executed _before_ a hook within the suite starts (e.g.
// runs before calling beforeEach in Mocha) beforeHook: function () { },
// Hook that gets executed _after_ a hook within the suite starts (e.g.
// runs after calling afterEach in Mocha) afterHook: function () { },
// Function to be executed before a test (in Mocha/Jasmine) or a step (in
// Cucumber) starts. beforeTest: function (test) { }, Runs before a
// WebdriverIO command gets executed. beforeCommand: function (commandName,
// args) { }, Runs after a WebdriverIO command gets executed afterCommand:
// function (commandName, args, result, error) { }, Function to be
// executed after a test (in Mocha/Jasmine) or a step (in Cucumber) starts.
// afterTest: function (test) { }, Hook that gets executed after the suite
// has ended afterSuite: function (suite) { }, Gets executed after all
// tests are done. You still have access to all global variables from the
// test. after: function (result, capabilities, specs) { }, 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(exitCode) { }
};
// Tweak the configuration if we're in Travis-CI.
if ( process.env.CI ) {
// Set the tests' base url.
// const BASE_URL = 'http://wordpress.local';
// Remove any previously set baseUrl (we use one different URL for each
// browser).
// delete config.baseUrl;
// Configure Sauce Labs.
config.user = process.env.SAUCE_USERNAME;
config.key = process.env.SAUCE_ACCESS_KEY;
// Use Sauce.
config.services = [ 'firefox-profile', 'sauce' ];
// Add browsers: Firefox, Internet Explorer.
config.capabilities = [
{
browserName: 'chrome',
version: 'latest',
platform: 'Windows 10'
}, {
browserName: 'chrome',
version: 'latest-1',
platform: 'Windows 10'
}, {
browserName: 'safari',
platform: 'macOS 10.12',
version: 'latest'
// }, {
// browserName: 'firefox',
// version: 'latest',
// platform: 'Windows 10'
}, {
browserName: 'internet explorer',
version: 'latest',
platform: 'Windows 10'
}, {
browserName: 'MicrosoftEdge',
version: 'latest',
platform: 'Windows 10'
}
];
// Set Travis job and build numbers.
for ( var i = 0; i < config.capabilities.length; i ++ ) {
config.capabilities[ i ][ 'tunnel-identifier' ] = process.env.TRAVIS_JOB_NUMBER;
config.capabilities[ i ].build = process.env.TRAVIS_BUILD_NUMBER;
config.capabilities[ i ].name = process.env.TRAVIS_BRANCH + ' (build ' + process.env.TRAVIS_BUILD_NUMBER + '; commit ' + process.env.TRAVIS_COMMIT + ')';
config.capabilities[ i ].public = true;
config.capabilities[ i ].baseUrl = 'http://wordpress.local/' + (
i + 1
);
}
}
exports.config = config;