Closed Bug 976133 Opened 10 years ago Closed 10 years ago

[meta] Implement Loop standalone-page unit tests

Categories

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

Product:
Hello (Loop)
Component:
Client
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: abr, Assigned: dmosedale)

References

Details

We need to implement client unit tests for the standalone web-page UI (the one the "call me" link clicker receives) that are run as part of our normal CI process. The Talkilla team used mocha and chai for this.

Ultimately, these tests need to encompass Firefox Desktop, Firefox Android, Firefox OS, Chrome Desktop, and Chrome Android.
In addition to all the reasons cited in bug 976127, using mocha and chai for the standalone stuff has the additional benefit that these tools are known to have strong cross-browser support for web-page apps.

I'd like us to go forward with this too.  See bug 976127 for thoughts on getting started.
Assignee: nobody → dmose
Priority: -- → P2
Unit tests are already being written using mocha and chai.  The only thing to do here, I suspect, is figure out what to do about continuous integration.  Once we know the ultimate repo story, the CI plan may fall out of that.  If we need something before thing, we could fall back to Travis.
This stuff will get unit tested on Firefox using Tinderbox CI thanks to a combination of bug 976127 (already landed) and bug 994483 (blocked on other stuff).  There's a third piece which is really about testing with non-Firefox browsers, which I've spun off into bug 994962, which I don't think blocks MLP.

In other words, I don't think there's really a need for this bug any longer.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.