Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preconfigure chrome browser #1860

Merged

Conversation

emanlove
Copy link
Member

Setup the chromer broswer and driver prior to executing tests so that selenium-manager does not configure test systems at execution time. It was also hoped that this would prevent selenium-manager from logging but for that to happen with current selenium-manager (Selenium v4.14.0) one must tell the Open Browser keyword where the driver is (using executable_directory argument).

We want to setup Chrome before we execute the tasks so that we can avoid
selenium-manager doing at the time of execution and changing the debug
log messages.
To avoid having the extra logging for selenium-manager (or at least to
control the debug output) we are setting the executable_path or the path
to the driver. Trying with the event_firing_webdriver script to see if
we see debug output there.
There is apparently a method for setting variables. Basically,

echo "{environment_variable_name}={value}" >> "$GITHUB_ENV"

Trying this out ..

Reference:
https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-environment-variable
@emanlove emanlove merged commit 036771b into robotframework:master Nov 1, 2023
0 of 9 checks passed
@emanlove emanlove deleted the preconfigure-chrome-browser branch November 1, 2023 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant