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

Revert "[webdriver] Close old windows at the end of each test as well… #25544

Merged
merged 1 commit into from
Sep 15, 2020

Conversation

stephenmcgruer
Copy link
Contributor

… as beginning (#24879)"

This reverts commit c35a4f0.

Unfortunately this broke the debugging flow of --pause-after-test; the
window is closed at the end of the test so the user can't see the
results or edit/refresh etc.

… as beginning (#24879)"

This reverts commit c35a4f0.

Unfortunately this broke the debugging flow of --pause-after-test; the
window is closed at the end of the test so the user can't see the
results or edit/refresh etc.
@wpt-pr-bot wpt-pr-bot added infra wptrunner The automated test runner, commonly called through ./wpt run labels Sep 15, 2020
@stephenmcgruer stephenmcgruer merged commit 3851e62 into master Sep 15, 2020
@stephenmcgruer stephenmcgruer deleted the smcgruer/revert-window-closing branch September 15, 2020 15:31
stephenmcgruer added a commit that referenced this pull request Sep 18, 2020
… as beginning" (#25567)

This is a reland of #24879 (which was reverted in #25544). It updates the code
to only close the windows if the user hasn't asked us to pause after a test has run.

From the original PR:

----

Previously, we closed old windows at the start of each test. This was nice in terms
of defensiveness (don't assume the last run left the world in a good state), but made
it hard to find problematic tests that left dialogs open (since they wouldn't throw until
the next test).

Instead, this patch does both - close both at the start and end of a test. This should
improve the blaming situation, whilst still being defensive.

There are potential performance implications to this patch, however test runs are
inconclusive. Full runs of Chrome and Safari show +- 2%, which is possibly within
margin of error. Running locally, some directories showed a ~2% slowdown, whilst
others had little or no difference.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infra wptrunner The automated test runner, commonly called through ./wpt run
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants