MicrosoftEdge driver instance not getting closed automatically
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- testing
Research direction
Start by reproducing the second-run failure with CodeceptJS 3.0.2, Node.js 12.16.3, Windows 10, Microsoft Edge, and webdriverio. Inspect the project configuration and the Microsoft Webdriver process handling; done means Edge can be used again after a test run without manually ending the driver task.
Written by the indexing model from the issue text.
Description
What are you trying to achieve?
When I execute multiple test cases on Microsoft Edge browser first time, test cases executes properly one after another and for every test case execution browser is getting opened.
What do you get instead?
After completion of first run when I execute command to run test cases again (second run) browser is not getting opened.
Error encountered:
EBUSY: resource busy or locked, open "path of the edge driver"
Other Information:
- After executing scripts on Edge if we try to execute scripts on different browser in second run still get same error
- When I Manually perform end task for "Microsoft Webdriver" and run execution command again then script execution startes properly
Details
- CodeceptJS version: "^3.0.2"
- NodeJS Version:v12.16.3
- Operating System: Windows 10
- puppeteer || webdriverio || protractor || testcafe version (if related) webdriverio
- Configuration file:
- 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
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Automattic/safe-publish#594 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
dream-num/dsh-univer-office#104 ·
-
comp/dashboard invalid P3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NousResearch/hermes-agent#121143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
avniproject/avni-webapp#1811 ·
-
area/auroraboot area/webui bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100