Closed Bug 1123282 Opened 10 years ago Closed 10 years ago

Please update flags for "Firefox UI tests" similar to "Mozmill Tests"

Categories

(bugzilla.mozilla.org :: Administration, task)

Production
task
Not set
normal

Tracking

()

VERIFIED FIXED

People

(Reporter: whimboo, Assigned: dkl)

Details

The newly created component "Mozilla QA > Firefox UI Tests" doesn't have all the flags we had before on the "Mozmill Tests" component. Given that we need them all, can you please add the missing flags accordingly? Thanks.
Fixed.
Assignee: nobody → dkl
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
I don't see all the changes yet. Maybe my summary was too wage. It might be better to say what explicitly has to be added: * All flags as used by Firefox for branch tracking and status * Target milestone and version as for Firefox
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Henrik Skupin (:whimboo) from comment #2) > I don't see all the changes yet. Maybe my summary was too wage. It might be > better to say what explicitly has to be added: > > * All flags as used by Firefox for branch tracking and status I see similar flags when selecting either Mozmill Tests or Firefox UI Tests in the new bug entry page. Which flags specifically are missing and I will fix them? > * Target milestone and version as for Firefox The original comment of this bug did not specify milestones and versions as well. So you need that all versions and all milestones in the Firefox product need to be added to the Mozilla QA product? That's quite a lot of new milestones and versions. dkl
Flags: needinfo?(hskupin)
(In reply to David Lawrence [:dkl] from comment #3) > > I don't see all the changes yet. Maybe my summary was too wage. It might be > > better to say what explicitly has to be added: > > > > * All flags as used by Firefox for branch tracking and status > > I see similar flags when selecting either Mozmill Tests or Firefox UI Tests > in the new bug entry page. Which flags specifically are missing and I will > fix them? I'm referring to the status-firefox-xyz and tracking-firefox-xyz flags reachable on the right side of a bug. Just checked and it's named as tracking flags. > > * Target milestone and version as for Firefox > > The original comment of this bug did not specify milestones and versions as > well. So you need that all versions and all milestones in the Firefox > product need to be added to the Mozilla QA product? That's quite a lot of > new milestones and versions. Oh. You don't have to add all of them. We can get started with version 38.0, but newer versions should automatically be pulled in. Please compare eg. bug 879972 with bug 1123401.
Flags: needinfo?(hskupin)
(In reply to Henrik Skupin (:whimboo) from comment #4) > (In reply to David Lawrence [:dkl] from comment #3) > > > I don't see all the changes yet. Maybe my summary was too wage. It might be > > > better to say what explicitly has to be added: > > > > > > * All flags as used by Firefox for branch tracking and status > > > > I see similar flags when selecting either Mozmill Tests or Firefox UI Tests > > in the new bug entry page. Which flags specifically are missing and I will > > fix them? > > I'm referring to the status-firefox-xyz and tracking-firefox-xyz flags > reachable on the right side of a bug. Just checked and it's named as > tracking flags. > > > > * Target milestone and version as for Firefox > > > > The original comment of this bug did not specify milestones and versions as > > well. So you need that all versions and all milestones in the Firefox > > product need to be added to the Mozilla QA product? That's quite a lot of > > new milestones and versions. > > Oh. You don't have to add all of them. We can get started with version 38.0, > but newer versions should automatically be pulled in. > > Please compare eg. bug 879972 with bug 1123401. Sorry for the confusion. You should be all set now. dkl
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
No problems at all. It looks great now. Thanks a lot!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.