972028 - [meta] System needs automated integration testing

Status: RESOLVED DUPLICATE of bug 1029183

(Hello (Loop) :: General, defect)

Comment 1

[Dan Mosedale (:dmosedale, :dmose)]

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.

Comment 2

[Alexis Metaireau (:alexis)]

Can we define clearly what we expect to be in the integration tests?

Comment 3

[Tarek Ziadé (:tarek)]

Not sure what we mean here, Adam can you detail ? thanks

Comment 4

[Adam Roach [:abr]]

(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.

Comment 5

[Dan Mosedale (:dmosedale, :dmose)]

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...