@@ -5,7 +5,7 @@ exports.config = {
55 // ====================
66 // WebdriverIO supports running e2e tests as well as unit and component tests.
77 runner : 'local' ,
8-
8+
99 //
1010 // ==================
1111 // Specify Test Files
@@ -23,7 +23,7 @@ exports.config = {
2323 // will be called from there.
2424 //
2525 specs : [
26- [ 'test/*.test.js' ] ,
26+ [ 'test/*.test.js' ] ,
2727 ] ,
2828 // Patterns to exclude.
2929 exclude : [
@@ -51,8 +51,8 @@ exports.config = {
5151 // Sauce Labs platform configurator - a great tool to configure your capabilities:
5252 // https://saucelabs.com/platform/platform-configurator
5353 //
54- capabilities : [ {
55-
54+ capabilities : [ {
55+
5656 // maxInstances can get overwritten per capability. So if you have an in-house Selenium
5757 // grid with only 5 firefox instances available you can make sure that not more than
5858 // 5 instances get started at a time.
@@ -61,13 +61,13 @@ exports.config = {
6161 browserName : 'chrome' ,
6262 acceptInsecureCerts : true ,
6363 'goog:chromeOptions' : {
64- args : [ '--headless' , '--disable-gpu' ]
64+ args : [ '--headless' , '--disable-gpu' ]
6565 }
6666 // If outputDir is provided WebdriverIO can capture driver session logs
6767 // it is possible to configure which logTypes to include/exclude.
6868 // excludeDriverLogs: ['*'], // pass '*' to exclude all driver session logs
6969 // excludeDriverLogs: ['bugreport', 'server'],
70- } ] ,
70+ } ] ,
7171 //
7272 // ===================
7373 // Test Configurations
@@ -99,7 +99,7 @@ exports.config = {
9999 // with `/`, the base url gets prepended, not including the path portion of your baseUrl.
100100 // If your `url` parameter starts without a scheme or `/` (like `some/path`), the base url
101101 // gets prepended directly.
102- baseUrl : 'https://demo .applitools.com' ,
102+ baseUrl : 'https://sandbox .applitools.com/bank ' ,
103103 //
104104 // Default timeout for all waitFor* commands.
105105 waitforTimeout : 10000 ,
@@ -115,8 +115,8 @@ exports.config = {
115115 // Services take over a specific job you don't want to take care of. They enhance
116116 // your test setup with almost no effort. Unlike plugins, they don't add new
117117 // commands. Instead, they hook themselves up into the test process.
118- services : [ 'chromedriver' ] ,
119-
118+ services : [ 'chromedriver' ] ,
119+
120120 // Framework you want to run your specs with.
121121 // The following are supported: Mocha, Jasmine, and Cucumber
122122 // see also: https://webdriver.io/docs/frameworks
@@ -137,10 +137,10 @@ exports.config = {
137137 // Test reporter for stdout.
138138 // The only one supported by default is 'dot'
139139 // see also: https://webdriver.io/docs/dot-reporter
140- reporters : [ 'spec' ] ,
140+ reporters : [ 'spec' ] ,
141+
141142
142143
143-
144144 //
145145 // Options to be passed to Mocha.
146146 // See the full list at http://mochajs.org/
0 commit comments