Skip to content
This repository has been archived by the owner on Nov 3, 2021. It is now read-only.

Bug 1180236 - Timing adjustments R=mhenretty #34005

Merged
merged 1 commit into from
Feb 4, 2016

Conversation

tilmankamp
Copy link
Contributor

Both tests in browser_chrome_new_window_test.js were intermittent. The 'open new window and edge swipe' one relies on a certain event order and timing. Test node performance differences could (still) result in different event orders. However: This change tries to lower that probability as much as possible.

@mozilla-autolander-deprecated
Copy link
Contributor

test('open new window', function() {
// Use the home-screen search box to open up the system browser
var url = server.url('sample.html');
rocketbar.homescreenFocus();
rocketbar.enterText(url, true);

// Count the number of currently open apps
// Wait for all app windows to show up
client.helper.wait(1000);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This kinda thing always makes me nervous. We need to wait on specific things happening, not an arbitrary amount of time. Is there nothing specifically we can check for in the DOM?

@mozilla-autolander-deprecated
Copy link
Contributor

test('open new window', function() {
// Use the home-screen search box to open up the system browser
var url = server.url('sample.html');
rocketbar.homescreenFocus();
rocketbar.enterText(url, true);
system.waitForBrowser(url);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better than just waiting for 1000ms.

tilmankamp added a commit that referenced this pull request Feb 4, 2016
Bug 1180236 - Timing adjustments R=mhenretty
@tilmankamp tilmankamp merged commit 8708b79 into mozilla-b2g:master Feb 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants