-
Notifications
You must be signed in to change notification settings - Fork 0
Selenium rewrite #233
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
base: master
Are you sure you want to change the base?
Selenium rewrite #233
Conversation
Alpha release v0.1.0 (first after split from Screenplay core) This is the first release of the new Screenplay Selenium project since it was split from Screenplay core and moved to its own repo. It mainly does everything that the old used to do. The one exception being the forthcoming browser flags fuctionality. This will replace the old "browser capabilities" (not web driver capabilities) functionality we used to have.
The fix to the crash bug which was blocking me means that now the web browser flags are loading correctly and are visible to the web driver.
Also a rework to Assets and screenshots.
According to https://learn.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-9.0#configuration-keys-and-values this is the correct syntax for env vars
Adds the `--no-sandbox` argument to run Chrome as root. See https://developer.chrome.com/docs/chromedriver/help/chrome-doesnt-start for more info
I am confident that it was using the right version, so this change is no longer needed.
Undo this change, I can't do it that way. I must use `AddArgument(string)` instead.
This follows lessons learned in the CSF.Extensions.WebDriver project. * Activate xvfb to provide an X environment for the browser * Ensure we're using the right driver version for the env * Upgrade to latest beta of CSF.Extensions.WebDriver
|
|




This is the PR for #212 and related issues. It introduces a complete rewrite of the Selenium library, which has been imported (with history) from CSF.Screenplay.Selenium.