You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
constserviceBuilder=newServiceBuilder(chromeDriverBinaryPath);// Setting this allows logging to make it to stdio of process running testsserviceBuilder.setStdio('inherit');// Provides more detailed logging if neededserviceBuilder.enableVerboseLogging();this._driver=awaitnewpage_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
The text was updated successfully, but these errors were encountered:
It would be helpful if chrome driver builder options were configurable both via CLI and via Extester API. In chrome driver we can run driver in headless mode. For running Extester in CI/CD pipeline headless mode would offer better performance than xvfb.
Is there any time line when this feature can be expected.
It would be helpful if chrome driver builder options were configurable both via CLI and via Extester API. In chrome driver we can run driver in headless mode. For running Extester in CI/CD pipeline headless mode would offer better performance than xvfb. Is there any time line when this feature can be expected.
I agree we can expose more options to configure for selenium-webdriver
regarding headless mode, afaik it won't be working for VS Code e2e testing because you cannot run UI tests in headless mode for Electron app
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
andenableVerboseLogging
methods can be helpful for diagnosing root causes of errors that currently get swallowed: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
The text was updated successfully, but these errors were encountered: