Repository navigation
alert issue in acceptance tests #1349
Description
I just withnessed following issue:
Running Acceptance . Keywords . Alerts . Alert Should Not Be Present with custom timeout left a alert open after a test failure and that caused a trickle down effect of quite a lot of tests failing due to following error:
UnexpectedAlertPresentException: Alert Text: None Message: unexpected alert open: {Alert text : Alert after 500ms!} (Session info: chrome=72.0.3626.121) (Driver info: chromedriver=2.46.628411 (3324f4c8be9ff2f70a05a30ebc72ffb013e1a71e),platform=Mac OS X 10.14.3 x86_64)
Maybe the alert tests should have test suite and teardown to open & close the browser to avoid this sort of flakyness ?
Activity
aaltat commentedon Mar 20, 2019
That is know to happen when there is a failure in alert handling. Making that better would be good, because if alert is left open then many tests will fail. And multiple failures makes it difficult to find the correct failure, specially in the Travis.