Confirmed users
2,177
edits
QA/Execution/Web Testing/Meetings/2016-02-04: Difference between revisions
QA/Execution/Web Testing/Meetings/2016-02-04 (view source)
Revision as of 15:21, 3 February 2016
, 3 February 2016→Discussion items
ValentinaP (talk | contribs) |
|||
| Line 23: | Line 23: | ||
= Discussion items = | = Discussion items = | ||
* | * [davehunt] Most of our automation suites are on pytest 2.7.3 and all are pinned to a specific version. We were prevented from updating to pytest 2.8 due to our use of pytest-timeout, however I disabled this a couple of weeks ago. As there have been no stalled builds (that I'm aware of), perhaps it's time to update pytest! Should we continue to pin to specific versions? An alternative would be to pin to a major version such as 2.8, allowing our builds to automatically download and install bugfix releases. There's already 2.8.6, so if we'd been closely following releases we would have potentially updated our suites 6 times. New features or changes in behaviour should only occur in major releases, so theoretically this would be safe, however there's a risk that a point release will include a regression. | ||
= [https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2016/Q1 Goals Check-in] - 1st and 3rd meetings, monthly = | = [https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2016/Q1 Goals Check-in] - 1st and 3rd meetings, monthly = | ||