Closed
Bug 972028
Opened 11 years ago
Closed 10 years ago
[meta] System needs automated integration testing
Categories
(Hello (Loop) :: General, defect)
Hello (Loop)
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1029183
People
(Reporter: abr, Unassigned)
References
Details
No description provided.
Comment 1•11 years ago
|
||
It's not obvious to me that integration testing wants to block the MLP (though it certain would block MVP). My suspicion is that functional and unit testing are likely sufficient for MLP.
Updated•11 years ago
|
Comment 3•10 years ago
|
||
Not sure what we mean here, Adam can you detail ? thanks
Flags: needinfo?(adam)
Reporter | ||
Comment 4•10 years ago
|
||
(In reply to Tarek Ziadé (:tarek) from comment #3) > Not sure what we mean here, Adam can you detail ? thanks As a caveat: all of the 972xxx Loop bugs were entered based on the notes I took at the Loop kickoff meeting, and some of the detail is a bit fuzzy at this point. With that in mind, I think the idea here was to have a set of tests that runs the whole setup end-to-end; which is to say, selenium- or marionette-style control of the in-browser client to interact with the server, all the way through to a client running in a remote browser.
Flags: needinfo?(adam)
Comment 5•10 years ago
|
||
What Adam said. :-) I know Nils has been doing some thinking about this; adding him to the CC. When he and I have talked about this in the past, we've speculated that it might ideally be built on top of the stuff under construction in bug 976116 and its dependents. My guess is that it will make sense to wait until that work is done before deciding how to move forward here. That said, Nils may have a different perspective...
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•