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

Reset driver connection even if stopping the driver fails #87

Merged
merged 1 commit into from
Aug 29, 2024

Commits on Aug 14, 2024

  1. Reset driver connection even if stopping the driver fails

    This change ensures that if an error occurs whilst stopping the driver,
    that the current driver is still discarded and does not impact
    subsequent tests.
    
    We have experienced issues when testing large datasets whereby the
    page takes a significant amount of time to load, blocking the driver. As
    a result the connection timeout is encountered, and the Behat Scenario
    fails.
    
    We also restart the browser between every test to ensure that all caches
    are cleared. We do this in a Behat hook.
    
    When we come to restart the connection and start the next test the
    WebDriver connection is still hung causing another exception to be
    thrown during the reset and no way to discard the session and start a
    new one.
    
    Generally this happens very rarely, but when it does happen it currently
    causes the entire testrun to be aborted and a rerun runs the entire
    testsuite rather than just the test that originally caused the failure.
    andrewnicols committed Aug 14, 2024
    Configuration menu
    Copy the full SHA
    d311dc0 View commit details
    Browse the repository at this point in the history