venv/lib/python3.7/site-packages/seleniumbase/fixtures/base_case.py:1969: in hover_and_click
hover_selector, by=hover_by, timeout=timeout)
venv/lib/python3.7/site-packages/seleniumbase/fixtures/base_case.py:2169: in wait_for_element_visible
self.driver, selector, by, timeout)
it worked fine on 1.24.1
@PeterNgTr I might be your page changed. I was able to use it successfully.
Chrome version 76 was just released. Chrome users will get automatically upgraded. This may break your tests depending on which version of ChromeDriver is installed on your machines. I've updated the
seleniumbase install chromedriver method so that you get a compatible driver for the most number of Chrome versions. This takes effect in seleniumbase 1.26.4
Additionally,
w3c will be turned on during Chrome runs.
Let me know if you see any issues.
Only supported are hack around parametrised and using of auto use only fixtures all because of unittest.testcase
Injecting into request.cls is a complete hack and we are losing probably the single best use of pytest as a result
Happy to have an in-depth discussion on how it can become viable đ
It boils down to base case extending unittest testcase which kinda silos it into a non pytest friendly solution, ideally seleniumbase shouldnât be concerned with a test runner but I can understand itâs hard to change that, maybe we can come up with something
Just in general it is impossible to get fixture return values into tests, auto use fixtures are ok but of course you need a hack to get a value from them such as injecting into request.cls.foobar . Pytest doesnât support fixtures properly when running unittest tests (which base case forces everyone to do without choice)
The following pytest features work in unittest.TestCase subclasses:
Marks: skip, skipif, xfail;
Auto-use fixtures;
The following pytest features do not work, and probably never will due to different design philosophies:
Fixtures (except for autouse fixtures, see below);
Parametrization;
Custom hooks;
Third party plugins may or may not work well, depending on the plugin and the test suite.
This imo is the greatest limitation of seleniumbase and makes scalable pytest based projects almost impossible to do effectively
https://www.meetup.com/GDGCloudBoston/events/230839686/ You can thank the Google people for that. That meetup was from when I demoed SeleniumBase in front of a large crowd at Google.
The web-comic used for SeleniumBase example tests updated their website (https://xkcd.com/), so I had to make updates to the example tests to make them work all the way from start to finish again.
hi, I'm trying to use the selenium grid when running tests.
I'm following the guide here: https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/utilities/selenium_grid/ReadMe.md
selenium grid is up:
I'm following the guide here: https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/utilities/selenium_grid/ReadMe.md
selenium grid is up:
[SUCCESS] Selenium-WebDriver Grid Hub started successfully.
Grid Hub console: http://127.0.0.1:4444/grid/console
when starting the test
pytest -k 'test_C5764_Quantity_assertion' --server=127.0.0.1 --port=4444
it draws the error
tests/commons/base.py:72: in setUp
super(BaseTestCase, self).setUp()
venv/lib/python3.7/site-packages/seleniumbase/fixtures/base_case.py:3267: in setUp
disable_csp=self.disable_csp)
venv/lib/python3.7/site-packages/seleniumbase/fixtures/base_case.py:2783: in get_new_driver
disable_csp=disable_csp)
venv/lib/python3.7/site-packages/seleniumbase/core/browser_launcher.py:277: in get_driver
proxy_user, proxy_pass, user_agent, cap_file, disable_csp)
venv/lib/python3.7/site-packages/seleniumbase/core/browser_launcher.py:302: in get_remote_driver
desired_capabilities=capabilities)
venv/lib/python3.7/site-packages/selenium/webdriver/remote/webdriver.py:157: in __init__
self.start_session(capabilities, browser_profile)
venv/lib/python3.7/site-packages/selenium/webdriver/remote/webdriver.py:252: in start_session
response = self.execute(Command.NEW_SESSION, parameters)
venv/lib/python3.7/site-packages/selenium/webdriver/remote/webdriver.py:321: in execute
self.error_handler.check_response(response)
thanks Michael!
@PeterNgTr Use desired capabilities: https://github.com/seleniumbase/SeleniumBase/blob/master/examples/capabilities/ReadMe.md
@symonk
import time
from seleniumbase import BaseCase
class MyTestClass(BaseCase):
def test_alerts(self):
self.open("about:blank")
self.execute_script('window.alert("ALERT!!!")')
time.sleep(1.2) # Not needed (lets you see the alert pop up)
self.wait_for_and_accept_alert()
time.sleep(0.8) # Not needed (lets you see the alert go away)
Works for me
might need an update
Also, I just got married and am on my honeymoon in Rome. I arrived there today after a 4-hour layover in Amsterdam. Responses will be delayed!