Skip to content

[🐛 Bug]: unnecessary console.debug messages in seleniumManager.js #12676

@dtopuzov

Description

@dtopuzov

What happened?

Too many console.debug messages are printed when running tests.

I think it will be better if by default only warning/error messages are logged.

Some options to control the log level of NodeJS binding can be also useful.

How can we reproduce the issue?

Create a simple project with NodeJS bindings and run the tests.

Relevant log output

> npx jest tests/e2e

  console.debug
    Selenium Manager binary found at /Users/topuzov/git/kendo-e2e/node_modules/selenium-webdriver/bin/macos/selenium-manager

      at getBinary (node_modules/selenium-webdriver/common/seleniumManager.js:56:13)

  console.debug
    Selenium Manager binary found at /Users/topuzov/git/kendo-e2e/node_modules/selenium-webdriver/bin/macos/selenium-manager

      at getBinary (node_modules/selenium-webdriver/common/seleniumManager.js:56:13)

  console.debug
    Selenium Manager binary found at /Users/topuzov/git/kendo-e2e/node_modules/selenium-webdriver/bin/macos/selenium-manager

      at getBinary (node_modules/selenium-webdriver/common/seleniumManager.js:56:13)

  console.debug
    Selenium Manager binary found at /Users/topuzov/git/kendo-e2e/node_modules/selenium-webdriver/bin/macos/selenium-manager

      at getBinary (node_modules/selenium-webdriver/common/seleniumManager.js:56:13)

  console.debug
    Selenium Manager binary found at /Users/topuzov/git/kendo-e2e/node_modules/selenium-webdriver/bin/macos/selenium-manager

      at getBinary (node_modules/selenium-webdriver/common/seleniumManager.js:56:13)

  console.debug
    Selenium Manager binary found at /Users/topuzov/git/kendo-e2e/node_modules/selenium-webdriver/bin/macos/selenium-manager

      at getBinary (node_modules/selenium-webdriver/common/seleniumManager.js:56:13)

  console.debug
    Selenium Manager binary found at /Users/topuzov/git/kendo-e2e/node_modules/selenium-webdriver/bin/macos/selenium-manager

      at getBinary (node_modules/selenium-webdriver/common/seleniumManager.js:56:13)

  console.debug
    Driver path: /Users/topuzov/.cache/selenium/chromedriver/mac-x64/116.0.5845.96/chromedriver

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Browser path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Driver path: /Users/topuzov/.cache/selenium/chromedriver/mac-x64/116.0.5845.96/chromedriver

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Browser path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Driver path: /Users/topuzov/.cache/selenium/chromedriver/mac-x64/116.0.5845.96/chromedriver

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Driver path: /Users/topuzov/.cache/selenium/chromedriver/mac-x64/116.0.5845.96/chromedriver

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Browser path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Browser path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Driver path: /Users/topuzov/.cache/selenium/chromedriver/mac-x64/116.0.5845.96/chromedriver

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Browser path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Driver path: /Users/topuzov/.cache/selenium/chromedriver/mac-x64/116.0.5845.96/chromedriver

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Browser path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Driver path: /Users/topuzov/.cache/selenium/chromedriver/mac-x64/116.0.5845.96/chromedriver

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Browser path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Driver path: /Users/topuzov/.cache/selenium/chromedriver/mac-x64/116.0.5845.96/chromedriver

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

  console.debug
    Browser path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

      at logOutput (node_modules/selenium-webdriver/common/seleniumManager.js:148:15)

 PASS  tests/e2e/browser/screenshot.tests.ts
  ✓ should be able screenshot viewport (1871 ms)

 PASS  tests/e2e/components/grid.tests.ts
  ✓ should render cells (1918 ms)
  ✓ should render headers (233 ms)
  ✓ should be sorted (205 ms)

Operating System

All

Selenium version

4.12.0

What are the browser(s) and version(s) where you see this issue?

All

What are the browser driver(s) and version(s) where you see this issue?

All

Are you using Selenium Grid?

No

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-nodejsJavaScript BindingsI-defectSomething is not working as intended

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions