Closed Bug 1038070 Opened 11 years ago Closed 11 years ago

Test failure 'Link 1 title is visible for the tab' in testTabbedBrowsing/testBackgroundTabScrolling.js

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect, P1)

defect

Tracking

(firefox33 fixed, firefox34 fixed)

RESOLVED FIXED
Tracking Status
firefox33 --- fixed
firefox34 --- fixed

People

(Reporter: danisielm, Assigned: danisielm)

References

()

Details

(Keywords: regression, Whiteboard: [mozmill-test-failure][mozmill-test-skipped])

Attachments

(2 files, 7 obsolete files)

Module: functional Test: testTabbedBrowsing/testBackgroundTabScrolling.js Function: testScrollBackgroundTabIntoView Failure: "Link 1 title is visible for the tab" Branches: NIGHTLY Platforms: ALL http://mozmill-daily.blargon7.com/#/functional/report/233c96fc2ff8f1c1a44659ece20d04d4 Not sure if the first failure in report is related, running a testrun now to check. I'll provide a pushlog & skip patch right away.
Again, I miss the pushlog link between the builds when it has been started. Please always tell us about that when you file a P1 regression bug. It's easy to retrieve from the reports list.
Priority: -- → P1
I said in Comment 1 that I'll provide the pushlog right away. Here it is: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=cb75d6cfb004&tochange=e1a037c085d1 I see bug 1014313 as a candidate here. Skip patch creating now.
Or even better find the appropriate entries with nodecollector, so we do not fail again in the future if entries are getting changed.
Attached patch skip.patchSplinter Review
Here is a skip patch. We'll get into fixing this as you asked.
Attachment #8455208 - Flags: review?(andrei.eftimie)
Attachment #8455208 - Flags: review?(andreea.matei)
Comment on attachment 8455208 [details] [diff] [review] skip.patch Review of attachment 8455208 [details] [diff] [review]: ----------------------------------------------------------------- Disabled: https://hg.mozilla.org/qa/mozmill-tests/rev/47ebec26edd4 (default) (I updated the commit message to also include the bug number)
Attachment #8455208 - Flags: review?(andrei.eftimie)
Attachment #8455208 - Flags: review?(andreea.matei)
Attachment #8455208 - Flags: review+
Attachment #8455208 - Flags: checkin+
Well, I would have seen more value in increasing the initial index on this bug, to fix the problem and make use of nodecollector in a follow-up. Skipping tests is really the last resort, especially if the fix is so obvious. Please try to avoid that in the future.
(In reply to Henrik Skupin (:whimboo) [away 07/19 - 08/01] from comment #7) > Well, I would have seen more value in increasing the initial index on this > bug, to fix the problem and make use of nodecollector in a follow-up. > Skipping tests is really the last resort, especially if the fix is so > obvious. Please try to avoid that in the future. We've done this in the past and it has bit us back more than once if the initial seemingly "obvious" fix didn't work as expected. There was always pressure from you to skip the test ASAP even if we had a fix in the works as to not have failures once the daily testruns start. The statement that "Skipping tests is really the last resort" is conflicting with previous statements that we should have the testruns "clean" of failures (by disabling tests until they are fixed). If this sentiment has changed we should really talk about it on the mailing list or in a meeting, not in a comment on a P1 regression that needs to be disabled ASAP.
I will work on this.
Assignee: nobody → daniel.gherasim
Attached patch v1.patch (obsolete) — Splinter Review
Changed to use nodeCollector.
Attachment #8460093 - Flags: review?(andreea.matei)
Attached patch v1.1.patch (obsolete) — Splinter Review
Attachment #8460093 - Attachment is obsolete: true
Attachment #8460093 - Flags: review?(andreea.matei)
Attachment #8460094 - Flags: review?(andreea.matei)
Whiteboard: [mozmill-test-failure] → [mozmill-test-failure][mozmill-test-skipped]
Comment on attachment 8460094 [details] [diff] [review] v1.1.patch Review of attachment 8460094 [details] [diff] [review]: ----------------------------------------------------------------- Just a small change needed. ::: firefox/tests/functional/testTabbedBrowsing/testBackgroundTabScrolling.js @@ +95,3 @@ > > + // Check that the correct title is shown for all tabs > + for (var tab in nodeCollector.elements) { Please use forEach here with aTab.
Attachment #8460094 - Flags: review?(andreea.matei) → review-
Attached patch v2.patch (obsolete) — Splinter Review
Attachment #8460094 - Attachment is obsolete: true
Attachment #8460219 - Flags: review?(andrei.eftimie)
Attachment #8460219 - Flags: review?(andreea.matei)
Comment on attachment 8460219 [details] [diff] [review] v2.patch Review of attachment 8460219 [details] [diff] [review]: ----------------------------------------------------------------- I'd like to improve the checks a bit for readability. ::: firefox/tests/functional/testTabbedBrowsing/testBackgroundTabScrolling.js @@ +98,5 @@ > + var node = aTab.getNode(); > + expect.waitFor(() => { > + return (aIndex === 0 && node.label === "Open link in a new tab") || > + (aIndex === countTabs - 1 && node.label === "2") || > + (node.label === "1"); This is a bit hard to follow. Can we do a switch or some if clauses and do specific checks for the first element, the last element and defaults to the rest of the elements.
Attachment #8460219 - Flags: review?(andrei.eftimie)
Attachment #8460219 - Flags: review?(andreea.matei)
Attachment #8460219 - Flags: review-
Attached patch v2.1.patch (obsolete) — Splinter Review
Changed to make the same checks as before in the test.
Attachment #8460219 - Attachment is obsolete: true
Attachment #8461579 - Flags: review?(andrei.eftimie)
Attached patch v2.2.patch (obsolete) — Splinter Review
Attachment #8461579 - Attachment is obsolete: true
Attachment #8461579 - Flags: review?(andrei.eftimie)
Attachment #8461582 - Flags: review?(andrei.eftimie)
Comment on attachment 8461582 [details] [diff] [review] v2.2.patch Review of attachment 8461582 [details] [diff] [review]: ----------------------------------------------------------------- ::: firefox/tests/functional/testTabbedBrowsing/testBackgroundTabScrolling.js @@ +90,5 @@ > }, "The all tabs popup should have been opened"); > > + // Select all opened tabs > + var nodeCollector = new domUtils.nodeCollector(allTabsPopup.getNode()); > + nodeCollector.queryNodes(".alltabs-item :not(:first-child)"); I don't think this works as you'd expect. Given that there is a space in the selector, you actually get all non-first-child descendants of .alltabs-item
Attachment #8461582 - Flags: review?(andrei.eftimie) → review-
Attached patch v2.3.patch (obsolete) — Splinter Review
Fixed that.
Attachment #8461582 - Attachment is obsolete: true
Attachment #8464001 - Flags: review?(andrei.eftimie)
Comment on attachment 8464001 [details] [diff] [review] v2.3.patch Review of attachment 8464001 [details] [diff] [review]: ----------------------------------------------------------------- ::: firefox/tests/functional/testTabbedBrowsing/testBackgroundTabScrolling.js @@ +97,4 @@ > > + // Check that the correct title is shown for all tabs > + nodeCollector.nodes.forEach((aTab, aIndex) => { > + if (aIndex !== countTabs - 1) { I'm not fond of this `if` clause for every step when we can check this item before the loop and loop only over the rest of the items. Please check the last element before the loop. Do a pop on the array then you only have the second check in the loop.
Attachment #8464001 - Flags: review?(andrei.eftimie) → review-
Attached patch v2.4.patch (obsolete) — Splinter Review
Attachment #8464001 - Attachment is obsolete: true
Attachment #8465441 - Flags: review?(andrei.eftimie)
Comment on attachment 8465441 [details] [diff] [review] v2.4.patch Review of attachment 8465441 [details] [diff] [review]: ----------------------------------------------------------------- Just 2 small nits and we can land this. ::: firefox/tests/functional/testTabbedBrowsing/testBackgroundTabScrolling.js @@ +98,3 @@ > > + // Check that the correct title is shown for the last tab > + expect.equal(nodeCollector.nodes[nodeCollector.nodes.length - 1].label, "2", For readability please leave the length in a separate variable as you've had it before. @@ +102,5 @@ > + > + nodeCollector.nodes.pop(); > + > + // Check that the correct title is shown for rest of the tabs > + nodeCollector.nodes.forEach((aTab, aIndex) => { We don't need the index anymore.
Attachment #8465441 - Flags: review?(andrei.eftimie) → review-
Attached patch v2.5.patchSplinter Review
Attachment #8465441 - Attachment is obsolete: true
Attachment #8465463 - Flags: review?(andrei.eftimie)
Comment on attachment 8465463 [details] [diff] [review] v2.5.patch Review of attachment 8465463 [details] [diff] [review]: ----------------------------------------------------------------- r+ https://hg.mozilla.org/qa/mozmill-tests/rev/abeb8d51df89 (default)
Attachment #8465463 - Flags: review?(andrei.eftimie)
Attachment #8465463 - Flags: review+
Attachment #8465463 - Flags: checkin+
We'll also need to backport this to Aurora.
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: