but was wondering if you are still maintaining 5...
@my-ownaccount be assured that I would answer you if I know a solution
or just replace
"@wdio/cli": "^5.22.2", with "@wdio/cli": "^6.0.5",
Although I am seeing:
```
```
[0-0] 2020-03-30T16:11:46.424Z ERROR @wdio/local-runner: Failed launching test session: TypeError: Cannot read property 'watch' of undefined
at Runner.run (/home/me/dev/WDIO/node_modules/@wdio/runner/build/index.js:165:15)
```
??
at Runner.run (/home/me/dev/WDIO/node_modules/@wdio/runner/build/index.js:165:15)
```
??
if you have a bug fix for v5 we are happy to merge and release it
Oh hang on, are there any meaningful changes to wdio.conf.js for 6? Maybe my lazy upgrading produced the above error?
I'll look closer tomorrow - time to run for now!
@my-ownaccount
Hi here, I'm getting this error while running tests [0-137] 2020-03-30T08:32:38.851Z DEBUG @wdio/local-runner:utils: init remote session
[0-137] 2020-03-30T08:32:38.855Z INFO webdriverio: Initiate new session using the webdriver protocol
[0-137] 2020-03-30T08:32:38.872Z INFO webdriver: [POST] http://x.x.x.x:9000/wd/hub/session
[0-137] 2020-03-30T08:32:38.872Z INFO webdriver: DATA { capabilities:
{ alwaysMatch: { browserName: 'chrome', 'goog:chromeOptions': [Object] },
firstMatch: [ {} ] },
desiredCapabilities:
{ browserName: 'chrome',
'goog:chromeOptions': { args: [Array] } } }
[0-137] 2020-03-30T08:32:38.925Z DEBUG webdriver: request failed due to status 33
[0-137] 2020-03-30T08:32:38.926Z WARN webdriver: Request failed due to Unable to create new service: ChromeDriverService
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'ip-100-65-3-4.ec2.internal', ip: ’grid node ip’, os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-957.12.1.el7.x86_64', java.version: '1.8.0_222'
Driver info: driver.version: unknown
[0-137] 2020-03-30T08:32:38.926Z INFO webdriver: Retrying 1/3
any help is highly appreciated.
Hi here, I'm getting this error while running tests [0-137] 2020-03-30T08:32:38.851Z DEBUG @wdio/local-runner:utils: init remote session
[0-137] 2020-03-30T08:32:38.855Z INFO webdriverio: Initiate new session using the webdriver protocol
[0-137] 2020-03-30T08:32:38.872Z INFO webdriver: [POST] http://x.x.x.x:9000/wd/hub/session
[0-137] 2020-03-30T08:32:38.872Z INFO webdriver: DATA { capabilities:
{ alwaysMatch: { browserName: 'chrome', 'goog:chromeOptions': [Object] },
firstMatch: [ {} ] },
desiredCapabilities:
{ browserName: 'chrome',
'goog:chromeOptions': { args: [Array] } } }
[0-137] 2020-03-30T08:32:38.925Z DEBUG webdriver: request failed due to status 33
[0-137] 2020-03-30T08:32:38.926Z WARN webdriver: Request failed due to Unable to create new service: ChromeDriverService
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'ip-100-65-3-4.ec2.internal', ip: ’grid node ip’, os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-957.12.1.el7.x86_64', java.version: '1.8.0_222'
Driver info: driver.version: unknown
[0-137] 2020-03-30T08:32:38.926Z INFO webdriver: Retrying 1/3
any help is highly appreciated.
just set this in your capabilities:
’goog:chromeOptions’: { binary: “/path/to/chromium” } }
yup, that's what I was looking into doing it.
I know that
I know that
puppeteer package has a built-in chromium binary that can be accessed with require('puppeteer').executablePath(). But turns out that if I add puppeteer package, the puppeteer-core that it downloads does not have the debug folder and for some reason DevTools throws some exceptions.
Here it is:
$ wdio run wdio.conf.js
(node:53157) UnhandledPromiseRejectionWarning: Error: Cannot find module '/Users/mauricio.giacomello/Dev/wdio6/node_modules/puppeteer-core/node_modules/debug'
Require stack:
- /Users/mauricio.giacomello/Dev/wdio6/node_modules/devtools/build/index.js
- /Users/mauricio.giacomello/Dev/wdio6/node_modules/webdriverio/build/utils.js
- /Users/mauricio.giacomello/Dev/wdio6/node_modules/webdriverio/build/multiremote.js
- /Users/mauricio.giacomello/Dev/wdio6/node_modules/webdriverio/build/index.js
- /Users/mauricio.giacomello/Dev/wdio6/node_modules/@wdio/cli/build/commands/repl.js
- /Users/mauricio.giacomello/Dev/wdio6/node_modules/yargs/index.js
- /Users/mauricio.giacomello/Dev/wdio6/node_modules/@wdio/cli/build/index.js
- /Users/mauricio.giacomello/Dev/wdio6/node_modules/@wdio/cli/bin/wdio.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:625:15)
at Function.Module._load (internal/modules/cjs/loader.js:527:27)
at Module.require (internal/modules/cjs/loader.js:683:19)
at require (internal/modules/cjs/helpers.js:16:16)
at Object.<anonymous> (/Users/mauricio.giacomello/Dev/wdio6/node_modules/devtools/build/index.js:47:1)
at Module._compile (internal/modules/cjs/loader.js:777:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:788:10)
at Module.load (internal/modules/cjs/loader.js:643:32)
at Function.Module._load (internal/modules/cjs/loader.js:556:12)
at Module.require (internal/modules/cjs/loader.js:683:19)
(node:53157) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:53157) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
If I simply remove
Note that I am not even importing/requiring puppeteer in any of my scripts.
"puppeteer": "^2.1.1" from my package.json it does not throw this exception.Note that I am not even importing/requiring puppeteer in any of my scripts.
in "@wdio/allure-reporter" 5 and 6 in report shown
browser: Chrome-19.4.0
what is 19.4.0 ?
looks like it is from here
if (!this.isMultiremote) {
const { browserName, deviceName } = this.capabilities
const targetName = browserName || deviceName || cid
const browserstackVersion = this.capabilities.os_version || this.capabilities.osVersion
const version = browserstackVersion || this.capabilities.version || this.capabilities.platformVersion || ''
const paramName = deviceName ? 'device' : 'browser'
const paramValue = version ? `${targetName}-${version}` : targetName
currentTest.addParameter('argument', paramName, paramValue)
}
localrun on macos catalina 10.15.4
Their assertion library is the only thing you can use in an e2e world
Hi there! Let's say I have multiple test suites, each one testing a bit of plugin functionality on my site. Many test suites, but not all, share a similar setup: login to a test account, navigate to a product page, add the product to the cart. What is the preferred way to abstract away those steps from the individual test suites?
Would I define a Page Object class for LoginAndAddToCart, and all the test suites should inherit from that and call the function from that class?
Do you store Page Objects in the /spec folder that the rest of the tests reside in?
Hi again. Now that I'm using
$(browser.getActiveElement()).getText(), I'm facing an error: selector needs to be typeof 'string' or 'function'. This happens even when I simply try to print console.log($(browser.getActiveElement()).getText());. I've tried this with a few of my tests and I've confirmed that the element that I'm trying to get text from is focused. Am I doing something wrong, or is this an issue with v6?