You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Some tests are failing with Selenium::WebDriver::Error::UnknownError: unknown error: unhandled inspector error: {"code":-32000,"message":"Node with given id does not belong to the document"} causing test flakiness.
Identify the cause and eliminate the flakiness. Expected cause is a race condition where the error occurs when the tests asserts the 'creating...' modal does not exist but it temporarily exists before being removed.
To Reproduce
Steps to reproduce the behaviour:
From Integration Suite command line, execute:
# warning, this will open 10 Chrome windowsforiin$(seq 1 10);do (DEBUG_ON_FAIL=true ENVIRONMENT=uat bundle exec rspec ./spec/limber/bespoke_chromium_3pv3_pipeline_spec.rb:38 >$i.test_log &);done
The results will be recorded in test_log files for parsing/grepping.
The text was updated successfully, but these errors were encountered:
psd-issuerbot
changed the title
[BUG] Integration Suite error - Selenium::WebDriver::Error::UnknownError - Node with given id does not belong to the document
Y24-417 - [BUG] Integration Suite error - Selenium::WebDriver::Error::UnknownError - Node with given id does not belong to the document
Oct 23, 2024
Describe the bug
Some tests are failing with
Selenium::WebDriver::Error::UnknownError: unknown error: unhandled inspector error: {"code":-32000,"message":"Node with given id does not belong to the document"}
causing test flakiness.Identify the cause and eliminate the flakiness. Expected cause is a race condition where the error occurs when the tests asserts the 'creating...' modal does not exist but it temporarily exists before being removed.
To Reproduce
Steps to reproduce the behaviour:
test_log
files for parsing/grepping.Alternatively use https://github.com/sanger/interrogator to indentify examples of this error from the flagged
flaky
tests.Expected behaviour
The tests pass without that failure message.
Additional context
See example at:
https://gitlab.internal.sanger.ac.uk/psd/integration-suite/-/jobs/1648820/artifacts/file/tmp/capybara/limber_bespoke_chromium_3pv3_pipeline_spec_38.png
https://gitlab.internal.sanger.ac.uk/psd/integration-suite/-/jobs/1648820
The text was updated successfully, but these errors were encountered: