Jim Brännlund
Jim Brännlund
Maybe hold off on that, as I think the repo created for me in this issue: https://github.com/pytest-dev/pytest-selenium/issues/284 actually covers this issue as well.
Ping @larsrinn Any progress on this?
Could you describe the use case you're faced with @tony ? That might helps us suggest an alternative approach.
Since this request was made, has there been any changes to `pytest` that would make the implementation of a driver factory easier? @RonnyPfannschmidt @nicoddemus
> If you mean multi scope fixtures, then nope That or anything else that comes to mind. 🤷♂️
Could you exemplify what you're looking for? Maybe even in a PR? ;)
Would you mind giving an example of that? What problem are you trying to solve? As for `webdriver_manager`, without digging deeper into it - I think it's out of scope...
> Currently, at least according to the docs, it's only possible to specify a driver via CLI flag, and there are browsers missing that one might wanna use, like, Brave...
> Out of curiosity, are there drivers for Brave and Chromium? Ah, brave == chromium, https://abodeqa.com/selenium-tests-in-brave-browser/
> With regards to supporting `webdriver_manager` I think the biggest use case is to be able to let users run tests against different browsers without having to install them manually...