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
{{ message }}
This repository has been archived by the owner on Nov 27, 2019. It is now read-only.
New profiles now open a tab about the privacy policy and the awesomebar hints about using it for search. Both of these open extra windows that can break tests, since tests expect no extra tabs and windows to be open after them (i.e. only the main window with only the start page).
The first test will fail with "Should not be any unexpected tabs open".
A temporary workaround is to add require("sdk/test/utils").cleanUI(); before any tests are ran. Note that this is async and a faster test may run before it's done. So instead you might want to wait for the promise to resolve in your first test.
The text was updated successfully, but these errors were encountered:
Shouldn't. The issue, from what I understand of the error and what I've observed when running tests locally, is that there's an extra tab and the awesomebar is open (which actually bugs out some stuff, because it's a popup that stays open...)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
New profiles now open a tab about the privacy policy and the awesomebar hints about using it for search. Both of these open extra windows that can break tests, since tests expect no extra tabs and windows to be open after them (i.e. only the main window with only the start page).
The first test will fail with "Should not be any unexpected tabs open".
A temporary workaround is to add
require("sdk/test/utils").cleanUI();
before any tests are ran. Note that this is async and a faster test may run before it's done. So instead you might want to wait for the promise to resolve in your first test.The text was updated successfully, but these errors were encountered: