Closed Bug 1071990 Opened 10 years ago Closed 8 years ago

make loop end-to-end call test run in two browsers instead of one

Categories

(Hello (Loop) :: Client, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE
backlog tech-debt

People

(Reporter: dmosedale, Unassigned)

References

Details

(Whiteboard: [tech-debt])

User Story

As a developer, I can run an end-to-end test that uses two browser instead of one, making it exercise code paths notably more like would they would be exercised by real users.
This requires at least one bug in Marionette fixed (marked in the dependencies). The way Andrei and I were talking about structuring this test was to have the test itself (which is handed a Marionette instance by the harness), manually spin up a Marionette instance for the second browser to be called.
User Story: (updated)
Whiteboard: [tech-debt]
backlog: --- → Fx36+
backlog: Fx36+ → Fx37+
backlog: Fx37+ → Fx38?
Moving these to blocking-loop="tech-debt" so they can be triaged against other tech debt bugs. When we take a tech-debt bug to work on - just mark it "firefox-backlog"+ and give priority. Then we'll pull it during iteration planning (or factor it into workload if someone is already working on).
backlog: Fx38? → tech-debt
Blocks: 1154251
Rank: 21
Flags: firefox-backlog+
Priority: -- → P2
No longer blocks: 1154251
Tentatively taking for further investigation/breakdown later in the week.
Assignee: nobody → standard8
Assignee: standard8 → nobody
Rank: 21 → 29
OS: Mac OS X → All
Hardware: x86 → All
Blocks: 976134
Support for Hello/Loop has been discontinued. https://support.mozilla.org/kb/hello-status Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.