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)
await browser.url('https://example.com/my-ember-app/#/my/ember/route')
, it the page loads as expected
await browser.url()
is called with a different Ember route, the page reloads but the Ember route stays the same. It seems like the page hash isn't being honoured?
Hey everyone.
Still need help with that one.
I got a question regarding preparing data in onPrapare() hook.
We started to work with an old legacy project and the only way to prepare the test data for it, is the UI.
I need to create a couple of users before all the tests in all browser will be run, so only onPrepare() fits the purpose. But the problem is that global browser
isn't instantiated yet during onPrepare() hook. The solution can be to use webdriver in standalone mode:
const { remote } = require('webdriverio');
(async () => {
const standalone_browser = await remote({
logLevel: 'trace',
capabilities: {
browserName: 'chrome'
}
})
//
but unfortunatelly some part of the code that I need to use during setup are already wrote in a pageObject pattern. And to use it, I need to use standalone_browser
instead of a global browser, so pageObjects can use methods e.g. $
and $$
. And I don't really want to rewrite those pageObjects because they are using my own framework wrappers that adds information to report automatically.
So the question is, is there a way to instantiate browser and use it globally on the onPrepare() hook. My first idea was just set global.browser = standalone_browser
but unfortunately PageObjects still don't see $
method in this case.
When I use global.browser = standalone_browser
it will allow to use browser.url
in pageObject. But on first find methods it falls with ReferenceError: $ is not defined
so my suggestion that this method references to global browser
was wrong.
May be @christian-bromann can help with such specific question.
If a webdriver io project is created on Linux and we want to run the scripts on windows do I need to make any configuration changes? Or just go ahead and run:
npm install
npm run test
please help!
Hello all.. I know we can pass the baseurl via wdio/cli .. but is there a way to pass just a string say 'QA' rather the complete URL and choose the url within the wdio config.. I have tried setting the env variable but it doesnt work.. TEST_ENV="WWW2" npx wdio CA-Indv-wdio.conf.js
TEST_ENV=WWW2 : The term 'TEST_ENV=WWW2' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
performActions()
tests failing - there is currently a difference between running tests locally and running them via a selenium standalone container - locally requires value: 'Escape'
and selenium still requires value: '\uE00C'
for pressing the escape key. Was thinking about raising an issue for it, but wasn't sure if it should be a webdriver issue or a selenium issue? (example of failing test using container https://gitlab.com/MeldCE/first-draft/-/jobs/2450578640 when works locally [test is https://gitlab.com/MeldCE/first-draft/-/blob/e5726c55c90f3b57538b5775164f2558554e24eb/test/specs/pen.ts#L282])
Dear webdriverio community,
I am just getting started with wdio, and it seems I can even get the simplest functionality out of it. Every page I have tried to open up gives me a data:, - Chromium
blank page, and I don't even know where to begin addressing this issue. At the bare minimum, I tried following the Getting Started and have the same results there. I would like to get a basic "hello world" functionality, but I seem blocked.
I'm running Ubuntu 20.04
$ node -v
v18.1.0
$ npm ls webdriverio
webdriverio-tests@0.1.0
├─┬ @wdio/cli@7.19.7
│ └── webdriverio@7.19.7
├─┬ @wdio/local-runner@7.19.7
│ └─┬ @wdio/runner@7.19.7
│ └── webdriverio@7.19.7 deduped
└─┬ wdio-chromedriver-service@7.3.2
└── webdriverio@7.19.7 deduped
$ cat package.json
{
"name": "webdriverio-tests",
"version": "0.1.0",
"private": true,
"devDependencies": {
"@wdio/cli": "^7.19.7",
"@wdio/local-runner": "^7.19.7",
"@wdio/mocha-framework": "^7.19.7",
"@wdio/spec-reporter": "^7.19.7",
"chromedriver": "^101.0.0",
"wdio-chromedriver-service": "^7.3.2"
},
"scripts": {
"wdio": "wdio run wdio.conf.js"
}
}
And here is a pastebin of the log output
Request failed with status 500 due to unknown error: DevToolsActivePort file doesn't exist
tells me Chrome can’t launch properly which is not WebdriverIO related
We've been using WebdriverIO for a couple years, and I've observed that other QA teams will add babel support. My understanding is that this gives engineers the ability to use the latest JavaScript features, but it comes with more maintenance and debugging cost than just using the native JavaScript.
What features are folks using that require them to use the Babel transpiler, or are teams just including Babel because they think they need it? Can anyone provide some insight on what features they were missing that led them to use Babel in WebdriverIO? Thank you.
Can someone here please help...
shared-store-service getValue return undefined in onComplete hook
webdriverio/webdriverio#8099
As per above PR this should have been fixed right??
Im using version 7.19.7
Hello. I have a question about deleteCookies
. I see from source code https://github.com/webdriverio/webdriverio/blob/f9eae7a6747b4bf55975a891f25643bba2165936/packages/webdriverio/src/commands/browser/deleteCookies.ts#L49
If name
is not provided this.deleteAllCookies()
wil be called, but there is no await
and deleteAllCookies
is async function.
Is this a mistake and can I contribution or I'm missing something?
According to the cucumber documentation, it's possible to add descriptions to Features, Scenarios and other feature file properties.
I have added a description to my feature and I can see this description in the result file generated by wdio-cucumberjs-json-reporter
. However it doesn't look like Scenario descriptions are being captured and added to the result file generated by wdio-cucumberjs-json-reporter
. Has anyone done this before, or is this an issue? And if it is an issue, which package? For reference here are the cucumber packages I am using, "@cucumber/cucumber": "^7.3.2"
, "@cucumber/pretty-formatter": "1.0.0-alpha.0"
, "@wdio/cucumber-framework": "7.16.5"
, "wdio-cucumberjs-json-reporter": "^3.0.0"
.