Gaia tests

[Vivien]

Hey,

Some browser-chrome tests support have landed in Gaia with
https://github.com/andreasgal/gaia/pull/230 .
I have added some basic documentation at
https://wiki.mozilla.org/B2G/Gaia/Hacking#Running_tests

We are not currently running Marionette tests, mostly because most of
the Gaia Team (if not all) runs b2g desktop build from m-c (some from
m-i) while developing and it's easy to hook some browser-chrome tests to
the current Mozilla infrastructure while Marionette has not landed (yet)
on m-c.

The current Mochitest architecture also let people add generic function
in head.js but I'm pretty sure this one could be added to Marionette too.

Another thing that bother me is the needs to write Marionette.ok(exp),
Marionette.foo, Marionette.bar. It quickly become annoying to have to
type Marionette every time, I wish they could pollute the global namespace.

Once those will be fixed we will use the Marionette testing framework
and it should be pretty straightforward to switch.

comments are welcome, but tests are better,
Vivien.

[mdas]

On Jan 19, 4:14 am, Vivien <2...@vingtetun.org> wrote:
> Hey,
>
> Some browser-chrome tests support have landed in Gaia withhttps://github.com/andreasgal/gaia/pull/230.
> I have added some basic documentation at  https://wiki.mozilla.org/B2G/Gaia/Hacking#Running_tests
>
> We are not currently running Marionette tests, mostly because most of
> the Gaia Team (if not all) runs b2g desktop build from m-c (some from
> m-i) while developing and it's easy to hook some browser-chrome tests to
> the current Mozilla infrastructure while Marionette has not landed (yet)
> on m-c.
>

Marionette is adding support for these styles of tests, so there would
be minimal (if any) changes needed to these tests.

> The current Mochitest architecture also let people add generic function
> in head.js but I'm pretty sure this one could be added to Marionette too.
>

We can add support for this. Here's a link to the bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=721017

> Another thing that bother me is the needs to write Marionette.ok(exp),
> Marionette.foo, Marionette.bar. It quickly become annoying to have to
> type Marionette every time, I wish they could pollute the global namespace.
>

We've changed this, so now you have access to the ok, is, ... commands
directly :)

> Once those will be fixed we will use the Marionette testing framework
> and it should be pretty straightforward to switch.
>
> comments are welcome, but tests are better,
> Vivien.

So right now, the emulator is broken. Once it's up and running again,
we'll help out with the switch and get tests going in our CI system!

[mdas]

Potentially reposting, since I'm not sure what happened to my first
message:

On Jan 19, 4:14 am, Vivien <2...@vingtetun.org> wrote:

> Hey,
>
> Some browser-chrome tests support have landed in Gaia withhttps://github.com/andreasgal/gaia/pull/230.
> I have added some basic documentation at https://wiki.mozilla.org/B2G/Gaia/Hacking#Running_tests
>
> We are not currently running Marionette tests, mostly because most of
> the Gaia Team (if not all) runs b2g desktop build from m-c (some from
> m-i) while developing and it's easy to hook some browser-chrome tests to
> the current Mozilla infrastructure while Marionette has not landed (yet)
> on m-c.

Marionette will require little to no changes in these tests in order
for them to run, so you most likely won't need to modify anything.

>
> The current Mochitest architecture also let people add generic function
> in head.js but I'm pretty sure this one could be added to Marionette too.
>

We can add support for this. You can follow this bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=721017

> Another thing that bother me is the needs to write Marionette.ok(exp),
> Marionette.foo, Marionette.bar. It quickly become annoying to have to
> type Marionette every time, I wish they could pollute the global namespace.
>

We've changed this so you now have access to the ok, is, ... commands
directly.

> Once those will be fixed we will use the Marionette testing framework
> and it should be pretty straightforward to switch.
>
> comments are welcome, but tests are better,
> Vivien.

Currently, the emulator is broken. Once it is up again, we can loop
these tests into our CI system and start testing on each commit. We'll
add more details when we're able to test :)

[Chris Jones]

----- Original Message -----
> From: "mdas" <md...@mozilla.com>
> To: mozilla...@lists.mozilla.org
> Sent: Wednesday, January 25, 2012 7:26:22 AM
> Subject: Re: [b2g] Gaia tests
>
> On Jan 19, 4:14 am, Vivien <2...@vingtetun.org> wrote:
> > Hey,
> >

> Currently, the emulator is broken. Once it is up again, we can loop
> these tests into our CI system and start testing on each commit.
> We'll
> add more details when we're able to test :)

The emulator has been unb0rked. Let the testing begin!

Cheers,
Chris