Even though, we're facing some technical limitations on MJS and the emulator, I think there are 2 topics we're able to start today.
> *▾ Engineering* > • Port Gip tests to Gij > *QA to provide the list of tests to port > and create the related bugs in bugzilla* > To make sure, we're on the same page here, the goal of this task is to port Gip tests that can run on Mulet. Is that right? If so, QA listed the test in this spreadsheet <https://docs.google.com/spreadsheets/d/19Cl5OaLSiynwW5NItjPuOQYpKbEKG_2eneiuwqm3Gew/edit#gid=0> some time ago, we have about 70 tests that can ported to Gij. If that's a go, we'll create the bugs in the corresponding gaia components. > • Create new Gij tests from moztrap scenarios > *QA to select the moztrap scenario that > can be valuable to automate and technically feasible* > FWIW, the workflow will be: 1. Manual testers will list out the tests they would like to automate 2. The QA people who do automation will comment on the technical feasibility. 3. The list will be presented to engineering. *▾ Device* > • Replace Jenkins module by Treeherder for > sending jobs to Bitbar > QA also works on it in Q4. Our jenkins had been hard to maintain in Q3. On Wed, Oct 7, 2015 at 11:57 AM, Julien Wajsberg <[email protected]> wrote: > Le 07/10/2015 10:32, Gabriele Svelto a écrit : > > On 07/10/2015 08:49, Julien Wajsberg wrote: > >> In SMS, to be able to run some automated tests, we're currently > >> emulating these APIs from Gaia. This means we don't test the Gecko code > >> at all. This is better than having no test, but this is not good enough > IMO. > > In the emulator you can send real SMS messages that will go through the > > RIL, gecko & all. See the documentation here on how to do it: > > > > http://developer.android.com/tools/devices/emulator.html#sms > > > > BTW since this accepts arbitrary PDUs it's also possible to deliver WAP > > Push messages, class 0 messages, etc... You have to first encode your > > payload though as the emulator interface doesn't do that for you. > > > > If you need help in setting up the emulator or using it ping me, I'm > > using it everyday to emulate calls in the callscreen & dialer. > > > > Just to be clear, in this thread we're talking about automated testing :) > And I was also talking about accessing this functionality in an easy way > from the testing code. > > As part of this we'll also need a way to push some existing data to the > API -- for SMS I guess this can be done with some Chrome-level code that > runs an indexedDB code before the test starts, and then clears it up > after the tests finishes. > > -- > Julien > > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos > >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
