-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[dotnet] Use selenium manager in tests #11871
[dotnet] Use selenium manager in tests #11871
Conversation
Oh nice, this was annoying. If the tests are passing.... |
1 test failed:
Can somebody re-trigger tests again, just to understand whether it's flaky. BTW it is passing locally. |
Retriggered by myself.
Now it is failing twice (per 2 target framework). What is changed:
Any clues? |
I think I've seen it before. Likely a timing issue? It's not going to be related to this PR at least. |
I'll test this locally because Selenium Manager is not used in GitHub actions. The runner has drivers on the path. |
I tested it locally, I have no driver in %PATH%, selenium manager is used. Moreover I fixed flaky test. Next step is remove drivers from PATH in GitHub actions? Here I am asking help, because I am not sure where exactly drivers are copied in workflow. |
What is installed on the runners can be found in this repo — https://github.com/actions/runner-images/blob/main/images/win/Windows2022-Readme.md#environment-variables-1 |
We should figure out how to remove the directory from PATH or see if we can delete the driver itself. |
You are right, there is |
All done, driver are physically deleted. Tests passed.
|
My apologies, @nvborisenko, I made changes in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @nvborisenko!
* Copy manager binaries to tests output * Use selenium manager implicitly to execute tests * Trigger tests again * Revert "Trigger tests again" This reverts commit 6dde845. * Fix flaky ShouldBeAbleToUploadTheSameFileTwice tests * Remove preinstalled drivers * Remove all known pre-installed drivers * Damn powershell * Print verbose messages while deleting drivers * Return back globalization namespace --------- Co-authored-by: Diego Molina <[email protected]>
Thanks for contributing to Selenium!
Related to #11304
Now it's not necessary to store driver binaries on machine where tests are executing, Selenium Manager does it.
To tests these changes: remove
c:\Projects\WebDriverServers\
directory and tests should be passed.Types of changes
Checklist