If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Create branches according to the Firefox train versions

RESOLVED FIXED in Firefox 38


Firefox UI Tests
2 years ago
2 years ago


(Reporter: whimboo, Assigned: whimboo)


Dependency tree / graph

Firefox Tracking Flags

(firefox38 fixed, firefox39 fixed, firefox40 unaffected, firefox-esr38 fixed)



(1 attachment)



2 years ago
To support different versions of Firefox we have to create appropriate branches in the firefox-ui-tests repository. It will look that way:

master -> mozilla-central
mozilla-aurora -> releases/mozilla-aurora
mozilla-beta -> releases/mozilla-beta
mozilla-release -> releases/mozilla-release
mozilla-esr38 -> releases/mozilla-esr38

Given that we backported all important fixes for Marionette to 38.0, all of our tests should work across those newly to create branches. But I will double check before pushing to the upstream repo.

Armen can you please check my proposal and give feedback if those branch names are ok with you? Thanks
Flags: needinfo?(armenzg.bugzilla)

Comment 1

2 years ago
Before we do the branching I would like to fix bug 1145638 first, so we have a consistent basis for tests across the branches.
Depends on: 1145638

Comment 2

2 years ago
That works for me.
What do you think about documenting it on the docs that we're following this agreement?
Flags: needinfo?(armenzg.bugzilla)

Comment 3

2 years ago
In case of Aurora the only test which is failing is TestSafeBrowsingWarningPages.test_warning_pages. But that is because of the change in bug 1147212 and 1162070. I will have to get that reverted.

Comment 4

2 years ago
(In reply to Armen Zambrano G. (:armenzg - Toronto) from comment #2)
> That works for me.

Great. So I will get started with mozilla-aurora in a moment.

> What do you think about documenting it on the docs that we're following this
> agreement?

The documentation has to be added to the wiki of the firefox-ui-tests repository. I don't want to have it at a different location. As close to the code is always better. If you need something in your docs, you can simple link to that wiki page.


2 years ago
Depends on: 1163014
Yes, I meant the repo. I'm glad we're on the same page.

Comment 6

2 years ago
Created attachment 8603539 [details] [review]
mozilla-aurora branch

Just a formal review please. As mentioned already above the safebrowsing warning pages test is the only one which is failure for Aurora and needs to be reverted.
Attachment #8603539 - Flags: review?(cmanchester)

Comment 7

2 years ago
Comment on attachment 8603539 [details] [review]
mozilla-aurora branch

I'm going to remove this review request given that is simply the former version of the test.
Attachment #8603539 - Flags: review?(cmanchester)

Comment 8

2 years ago
The branch mozilla-aurora has been created:

mozilla-beta and mozilla-release I will do on Monday.

Comment 9

2 years ago
The branch mozilla-beta has also been created:

Comment 10

2 years ago
Also created mozilla-release and mozilla-esr38:

Please note that tests for those two branches will fail as long as we do not have an officially released build of Firefox 38 on the FTP server. Best option here would always be to use the latest candidate build but that is not possible yet. See also https://github.com/mozilla/mozdownload/issues/273.

Comment 11

2 years ago
All what we can do on this bug is done right now.
Last Resolved: 2 years ago
status-firefox38: --- → fixed
status-firefox39: --- → fixed
status-firefox40: --- → unaffected
status-firefox-esr38: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 39
Product: Mozilla QA → Testing
You need to log in before you can comment on or make changes to this bug.