Dietrich, That info is in the linked spreadsheet. Look for white rows in the 1/17 column.
Looks like bluetooth headsets weren't tested, for lack of equipment, and OTA update wasn't tested due to the lack of a source build to update from. On another note, smoketesting the update that way is a little weird. AFAIK, the update behavior actually belongs to the "from" build, not the "to" build, so you can't really test the update behavior of a given build until the day after. That may be what threw off the smoketestwer. Geo ----- Original Message ----- > From: "Dietrich Ayala" <[email protected]> > To: "rafael" <[email protected]> > Cc: "qa-b2g" <[email protected]>, [email protected], > [email protected] > Sent: Thursday, January 17, 2013 9:27:44 AM > Subject: Re: 1/17/2013 Unagi Smoke Test Results - 43 passed, 0 failed, > 0 partial > > Thanks Rafael. Which two tests were not run, and why? > > On Thu, Jan 17, 2013 at 1:56 AM, rafael <[email protected]> > wrote: > > Hi All, > > > > 43 out of 45 tests passed for the 1/17/2013 build. 0 failed, 0 > > partial > > > > and 2 untested > > > > - Smoketest: > > > > https://docs.google.com/spreadsheet/ccc?key=0AqDJxnTd7VDLdDRKOE1uanE3M3FtMDBOVjRIV253S1E#gid=65 > > > > Thanks, > > > > QA Team > > > > -- > > *Rafael Márquez Díaz*** > > *SERVICIO DE VERIFICACIÓN Y VALIDACIÓN DE PROYECTOS (Open Web > > Device)* > > _______________________________________________ > > dev-gaia mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-gaia > _______________________________________________ > Qa-b2g mailing list > [email protected] > https://mail.mozilla.org/listinfo/qa-b2g > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
