Skip to content

[🚀 Request] Expose more configuration for selenium-webdriver ServiceBuilder #1787

@bmingles

Description

@bmingles

Describe the request

The instantiation of the selenium-webdriver/chrome ServiceBuilder is currently encapsulated in the VSBrowser.start function. It would be nice to expose some of its configuration options, specifically ones related to logging.

For example, the setStdio and enableVerboseLogging methods can be helpful for diagnosing root causes of errors that currently get swallowed:

const serviceBuilder = new ServiceBuilder(chromeDriverBinaryPath);

// Setting this allows logging to make it to stdio of process running tests
serviceBuilder.setStdio('inherit');

// Provides more detailed logging if needed
serviceBuilder.enableVerboseLogging();

this._driver = await new page_objects_1.Builder()
  .setChromeService(serviceBuilder)
  .forBrowser(page_objects_1.Browser.CHROME)
  .setChromeOptions(options)
  .build();

I'm not familiar enough with the architecture to suggest how these might best be exposed, only that having some way to configure the ServiceBuilder would be helpful.

Usage

Enabling more verbose logging was key to being able to identify the root causes of this issue:
#1767

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    Status

    Backlog

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions