christian-bromann on main
run coverage as part of the com… (compare)
christian-bromann on main
minor tweak (compare)
christian-bromann on main
wait for project to be bootstra… (compare)
christian-bromann on main
run unit tests in the background (compare)
christian-bromann on main
fix start script (compare)
"expect-webdriverio": "^1.4.1", "webdriverio": "^7.0.1",
in my package.json, have installed them, which as far as I can see on the doc is all I need to do. The functions do not exist when I try to use them in my tests / page objects. Does anyone have any idea why? Or know what else I should check?
Hey there! Wondering how folks are tackling the problem of multiple capabilities
when using stuff like Browserstack?
My setup:
What I've implemented so far:
Mocha describe
level tag of @browserstack
to determine what tests run in BS. (filtered using --mochaOpts.grep '@browserstack'
in my npm script)
Defined my capabilities
object to define my browser/device matrix we wish to test against.
What I'd like to add:it
level @ios
@android
@firefox
@edge
etc tags to only run required device/browser combinations for a given test
What's the best way of achieving this?
Getting error on npx wdio config -y ( I am using @wdio/cli@7.3.0 and node as v14.16.1) Installing wdio packages:
fibers@5.0.0 install C:\Users\sprakesh\Projects\Test\node_modules\fibers
node build.js || nodejs build.js
win32-x64-83
exists; testing
Binary is fine; exiting
chromedriver@89.0.0 install C:\Users\sprakesh\Projects\Test\node_modules\chromedriver
node install.js
ChromeDriver binary exists. Validating...
ChromeDriver is already available at 'C:\Users\sprakesh\AppData\Local\Temp\89.0.4389.23\chromedriver\chromedriver.exe'.
Copying to target path C:\Users\sprakesh\Projects\Test\node_modules\chromedriver\lib\chromedriver
events.js:292
throw er; // Unhandled 'error' event
^
Error: EISDIR: illegal operation on a directory, read
Emitted 'error' event on ReadStream instance at:
at internal/fs/streams.js:202:14
at FSReqCallback.wrapper [as oncomplete] (fs.js:539:5) {
errno: -4068,
code: 'EISDIR',
syscall: 'read'
}
npm WARN rollback Rolling back @nodelib/fs.walk@1.2.6 failed (this is probably harmless): EPERM: operation not permitted, rmdir 'C:\Users\sprakesh\Projects\Test\node_modules\@nodelib'
npm WARN Test@1.0.0 No description
npm WARN Test@1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! chromedriver@89.0.0 install: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the chromedriver@89.0.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\sprakesh\AppData\Roaming\npm-cache_logs\2021-04-08T08_40_41_421Z-debug.log
wdio.js config
Initialize WebdriverIO and setup configuration in your current project.
Options:
--version Show version number [boolean]
--watch Run WebdriverIO in watch mode [boolean]
-h, --hostname automation driver host address [string]
-p, --port automation driver port [number]
--path path to WebDriver endpoints (default "/") [string]
-u, --user username if using a cloud service as automation backend
[string]
-k, --key corresponding access key to the user [string]
-l, --logLevel level of logging verbosity
[choices: "trace", "debug", "info", "warn", "error", "silent"]
--bail stop test runner after specific amount of tests have
failed [number]
--baseUrl shorten url command calls by setting a base url[string]
-w, --waitforTimeout timeout for all waitForXXX commands [number]
-f, --framework defines the framework (Mocha, Jasmine or Cucumber) to
run the specs [string]
-r, --reporters reporters to print out the results on stdout [array]
--suite overwrites the specs attribute and runs the defined
suite [array]
--spec run only a certain spec file - overrides specs piped
from stdin [array]
--exclude exclude certain spec file from the test run - overrides
exclude piped from stdin [array]
--mochaOpts Mocha options
--jasmineOpts Jasmine options
--cucumberOpts Cucumber options
--aut
Hi We've just done an upgrade from v6->v7 and everything seems fine so far except this one error:
error TS2688: Cannot find type definition file for 'webdriverio/sync'.
The file is in the program because:
Entry point of type library 'webdriverio/sync' specified in compilerOptions
tsconfig.automation.json:21:23
21 "types": ["node", "webdriverio/sync", "@wdio/mocha-framework", "expect-webdriverio"]
~~~~~~~~~~~~~~~~~~
File is entry point of type library specified here.
Found 1 error.
Not sure if anyone else has spotted this before or knows what the cause is?
operation not permitted, rmdir
Has anyone else seen an issue where hooks get displayed as tests within the Browserstack dashboard?
From the image above, all the sessions with GUIDs are mocha hooks, whilst the named sessions are legitimate tests
Hi, I am trying to set up gitlab CI to run my tests but I just cannot get it to work. When I was using chromedriver in aorund 50% of the tests I got "invalid session id". Locally I have never gotten this error. So now I tryied to switch to selenium-standalone.
My pipeline looks like this:
stages:
variables:
GIT_SUBMODULE_STRATEGY: recursive
test-dm-test:
image: node:12
services:
- selenium/standalone-chrome
stage: test
script:
- apt-get update
- npm i
- npx wdio run ./wdio.conf.js
- allure generate allure-results
artifacts:
expire_in: 14 days
paths:
- "allure-report"
But here the error is "Error: not found: java" as well as "ERROR webdriver: RequestError: connect ECONNREFUSED 127.0.0.1:4444 at ClientRequest"
Can anyone help me on that?
hey guys I am trying to get multi remote working, I am passing my caps as:
class MultiChromeCapabilities {
constructor(cliOptions) {
this.myChromeBrowser1 = {
capabilities: {
browserName: 'chrome'
}
},
this.myChromeBrowser2 = {
capabilities: {
browserName: 'chrome'
}
}
}
}
module.exports = MultiChromeCapabilities;
or
class MultiChromeCapabilities {
constructor(cliOptions) {
this.capabilities = {
myChromeBrowser1 = {
capabilities: {
browserName: 'chrome'
}
},
myChromeBrowser2 = {
capabilities: {
browserName: 'chrome'
}
}
}
}
}
module.exports = MultiChromeCapabilities;
Neither appears to be working:
ERROR @wdio/runner: Error: Couldn't identify browserName "undefined"
however browser is defined when I console log the caps:
myChromeBrowser1: { capabilities: { browserName: 'chrome' } },
myChromeBrowser2: { capabilities: { browserName: 'chrome' } }
Any ideas on what I may be doing wrong? Trying a vanilla install of wdio with just multi remote caps now...