Multiple scenario with multiple session mess up the webdriver configuration(Both V2.x and V3.x has the problem)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, nodejs
- Domain
- testing
Research direction
Start with the supplied two-scenario test using two session configurations with different hosts and ports. Trace how the outer scenario and internal customer session update and restore the WebDriver configuration, then reproduce the second-scenario failure and verify that each session uses its own complete host and port.
Written by the indexing model from the issue text.
Description
Here is my test code:
`Feature("test")
Scenario("test1", ({ I }) => {
I.wait(3)
session("customer", browserstack_desktop_configuration, async () => {
I.wait(3);
})
})
Scenario("test2", ({ I }) => {
I.wait(3)
session("customer", browserstack_desktop_configuration, async () => {
I.wait(3);
})
})`
browserstack_desktop_configuration and browserstack_desktop_configuration is global configurations, they have different host and port, like:
browserstack_desktop_configuration: {
host:"a",
port:8080
},
browserstack_desktop_configuration:{
host:"b",
port:80
}
During scenario 1 execution, it using browserstack_desktop_configuration correctly, and start internal 'customer' session with browserstack_desktop_configuration configuration correctly. The tracky is, Before scenario 2 execution, the webdriver configuration change to :
{hostname:"a",
host:"b",
port:80
}, underline webdriverio is using hostname and port to start remote browser, so it throws below error message:
`Can't connect to WebDriver.
Error: Failed to create session.
Unable to connect to "http://a:80/wd/hub", make sure browser driver is running on that address.
If you use services like chromedriver see initialiseServices logs above or in wdio.log file as the service might had problems to start the driver.
Please make sure Selenium Server (ChromeDriver or PhantomJS) is running and accessible`
- Dominant language
- JavaScript
- Stars
- 4.2k
- Forks
- 756
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 16
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from codeceptjs/CodeceptJS
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
codeceptjs/CodeceptJS#5420 · 1 comment ·
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
codeceptjs/CodeceptJS#5358 · 1 comment ·
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
codeceptjs/CodeceptJS#4958 · 10 comments · 2 reactions ·
-
stale
Difficulty 1/5 Under an hour Newbie friendliness 72/100
codeceptjs/CodeceptJS#4778 · 3 comments ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 38/100
codeceptjs/CodeceptJS#5618 · 1 comment ·
All issues in codeceptjs/CodeceptJS
Similar issues
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/open-webui#30750 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100