This bug will cover the necessary work to do to convert the following test into Marionette. http://hg.mozilla.org/qa/mozmill-tests/file/default/firefox/tests/functional/testTabbedBrowsing/testNewWindow.js
Here is my feedback after looking at this test: * The test only covers opening a new window by menu. Our unit tests already make use of shortcuts. So we outreach this test already. * I don't see a reason why to check for the default home page in that test. It is not related to opening and closing a window. * Further I don't see why this test is part of the tabbed browsing folder when it is covering windows. This may be a relict from Litmus. So I would suggest we do not spend time on this test to get it converted, given that we perfectly cover this already in our unit tests: https://github.com/mozilla/firefox-ui-tests/blob/master/firefox_puppeteer/tests/test_windows.py#L79 https://github.com/mozilla/firefox-ui-tests/blob/master/firefox_puppeteer/tests/test_windows.py#L172 The only thing I see here is that we may have to make it explicit to use the menu and not the default triggering method in line 174 and 177 of the above unit test. Rebecca would you mind to cover that?
I've added the code here: https://github.com/rbillings/firefox-ui-tests/tree/newwindow
Created attachment 8560073 [details] [review] Link to GitHub pull request: https://github.com/mozilla/firefox-ui-tests/pull/72 Updated two instances of open browser to use menu option, per Comment 1
Attachment #8560073 - Flags: review?(hskupin)
Assignee: nobody → rbillings
Status: NEW → ASSIGNED
Attachment #8560073 - Flags: review?(hskupin) → review+
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 38
You need to log in before you can comment on or make changes to this bug.