Le 12/06/2013 01:33, Tony Chung a écrit : > To add to jason's points, It's absolutely too much overhead for my team to > smoketest each checkin. The only feasible way is having automated tests that > run per checkin. This is worth discussing with the A-team / Gaia UI team if > that is feasible, and in what time frame. > > our current QA team does write automated tests, but it currently supports > 1.01 smoketests and we havent gotten around to testing new features. We're > still one build behind and can't catch up current release fast enough for > this. We would request the help of gaia dev in this effort. (device > level testing is better, but maybe running on desktop build is good enough)
Note that that's why some of us try to advocate writing JavaScript-based UI tests using the JS marionette client, located in the Gaia repository. As usual, the first test has some overhead, because the developer has to create all the boilerplate to make the test run. But once it's done, any developer could add new tests for this piece of code. At least that's how it works for the gaia unit tests, and I expect it to be the same for the Marionette UI Tests. Therefore, it would help that the QA team write only some Marionette JS tests for each app, committed in the gaia repository, that Gaia developers could leverage to write their own test when they land fixes and features. Deal ? -- Julien
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
