1129634 - Convert Mozmill test 'functional/testTabbedBrowsing/testNewTab.js' to Marionette

Status: RESOLVED WONTFIX

(Testing :: Firefox UI Tests, defect, P2)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

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/testNewTab.js

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

I had a look at it and came out with the following proposal:

* We don't need any of the Australis related lines of code, given that there is no fallback to earlier versions of Firefox necessary anymore.

* I do not see a need why we have to open a specific URL. It will not give us any additional info about a number of tabs open.

* We have already covered the opening methods for menu, shortcut, and newTabButton inside the tabbar module. So only the tabStrip method is missing. Given that this is very specific and is behaving differently on platform versions, we should not include tabStrip into the tabbar module but leave it as a test.

* I also don't see that we have to do checks for about:newtab. This is clearly something which should go into those other tests.


To get this implemented here my feedback:

* Get a reference to the tabstrip element by using find_element via anon types. As parent the self.browser.tabbar.toolbar should be used.

* Call open_tab() by using a callback trigger and doing a double click on the tabstrip element inside of it.

* Do checks like the tabbar unit tests are doing for a strategy: https://github.com/mozilla/firefox-ui-tests/blob/master/firefox_puppeteer/tests/test_tabbar.py#L37

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+1]]

It looks like we are blocked on this test by not being able to issue a double click. See bug 1129702 for details.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+1]]

There is good coverage in browser chrome tests so this is not needed, and we are also going to remove the tests.