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

tests: get E2E tests working using RUN_SELENIUM_LOCALLY option #668

Open
GraemeWatt opened this issue Jun 22, 2023 · 0 comments
Open

tests: get E2E tests working using RUN_SELENIUM_LOCALLY option #668

GraemeWatt opened this issue Jun 22, 2023 · 0 comments
Labels
complexity: medium priority: medium type: bug Indicates an unexpected problem or unintended behaviour

Comments

@GraemeWatt
Copy link
Member

The end-to-end tests currently fail when using ChromeDriver locally with the RUN_SELENIUM_LOCALLY = True option with error messages like:

FAILED tests/e2e/test_dashboard.py::test_dashboard[Chrome] - assert False
FAILED tests/e2e/test_general.py::test_tables[Chrome] - AssertionError: assert '' == 'Figure 8 panel (a)'
FAILED tests/e2e/test_records.py::test_record_update[Chrome] - selenium.common.exceptions.ElementClickInterceptedException: Message: eleme...
ERROR tests/e2e/test_general.py::test_tables[Chrome] - AssertionError: Errors in browser log:

It would be useful if ChromeDriver options could be set to allow these tests to pass.

@GraemeWatt GraemeWatt added type: bug Indicates an unexpected problem or unintended behaviour priority: medium complexity: medium labels Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: medium priority: medium type: bug Indicates an unexpected problem or unintended behaviour
Projects
Status: To do
Development

No branches or pull requests

1 participant