QA/Execution/Web Testing/Meetings/2016-01-07: Difference between revisions

No edit summary
Line 19: Line 19:


= Discussion items =
= Discussion items =
*
* [davehunt] Changes to AMO dev caused expected failures, but due to high timeouts and reruns the amo.dev job took over 8 hours!
** I've removed reruns from amo.dev.* and set the timeout to 60 seconds
** I'd like to do this for all jobs, but it will cause noise due to intermittent failures
** Thoughts/opinions? Can we handle the noise and tackle the intermittent failures?
** Note that it is possible to mark individual tests as flaky and to indicate a maximum number of reruns.
* [davehunt] [https://github.com/mozilla/marketplace-tests/commit/62295a50902a41cfd90f506368bc9bcff5e9580b Until recently], marketplace-tests waiting for an element to be visible would wait 600 seconds instead of 60
** This is a good example of why it's a bad idea to mix implicit and explicit waits
* [davehunt] Sauce Labs has announce they're dropping support for Appium 1.3.4 and older
** We're using 1.4.13 as our default version (latest recommended version is 1.4.16)
** For AMO we're using 1.3.7 due to issues experienced with 1.4.x, so we may want to look into this before support is dropped for 1.3.x entirely


= [https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2015/Q4 Goals Check-in] - 1st and 3rd meetings, monthly =
= [https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2015/Q4 Goals Check-in] - 1st and 3rd meetings, monthly =
Confirmed users
2,177

edits