Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ppiper/node-browsers not working for msedge

Open
#40 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
dockerfile, node.js
Domain
devops, testing-qa

Research direction

No file or test is named. Start by reproducing the WebdriverIO testcase in Jenkins with the ppiper/node-browsers image, then inspect the Edge and Firefox version and certificate configuration. Done means the relevant browser configurations are identified and the reported Edge and Firefox failures are either resolved or narrowed to a reproducible incompatibility.

Written by the indexing model from the issue text.

Description

Hi,

I'm using ppiper/node-browsers to run my Webdriverio testcase in jenkins. looks like it's not working for Msedge and getting error like this Message: unknown error: unrecognized MSEdge version: HeadlessChrome/109.0.5414.119

And also for firefox, browser is not able to find element

10:06:47  [0-0]   message: 'Unable to locate element: //*[@id="j_username"]',
10:06:47  [0-0]   stacktrace: 'WebDriverError@chrome://remote/content/shared/webdriver/Errors.jsm:186:5\n' +
10:06:47  [0-0]     'NoSuchElementError@chrome://remote/content/shared/webdriver/Errors.jsm:398:5\n' +
10:06:47  [0-0]     'element.find/</<@chrome://remote/content/marionette/element.js:300:16\n'

is it because of certificate issue in firefox?

Is there any particular version need to be use?

Can anyone suggest please?

Dominant language
Dockerfile
Stars
11
Forks
7
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SAP/devops-docker-node-browsers

All issues in SAP/devops-docker-node-browsers

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.