QA/Execution/Web Testing/Meetings/2016-02-04: Difference between revisions

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Meetings
Jump to navigation Jump to search
 
(5 intermediate revisions by 4 users not shown)
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.
* [davehunt] I'm going to start updating our test suites to pytest 2.8.7 with pytest-xdist 1.14 and pytest-rerunfailures 1.0.1 (where used).
** Once complete, I will remove our infrastructure requirements as these will be redundant.
* [sphilp] meeting format/needs


= [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 =
* https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2016/Q1
* https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2016/Q1
= Upcoming Events =
{{:QA/Execution/Web Testing/Events}}


= Blog Ideas =
= Blog Ideas =
Line 35: Line 34:


= Lightning talks =
= Lightning talks =
*  
* [bsilverberg] One and Done / react.js - Search demo #2


= Project status / goals for next week (keep it brief)  =
= Project status / goals for next week (keep it brief)  =
Line 68: Line 67:


= Action items =
= Action items =
*
* {{prev|}}[kthiessen] Try to update the default version of Appium we use to 1.4.16
* {{prev|}}[stephend] Finalize the "year in review" blog post
** team members: please populate the etherpad at https://public.etherpad-mozilla.org/p/webqa-year-in-review-2015
* {{new|}}[davehunt] Start updating all our suites to the latest pytest
* {{done|}}[davehunt] Add moving our suites into the developer workflow to the [[QA/Execution/Web_Testing/Automation/Baseline|baseline]].


= Next Meeting =
= Next Meeting =
* Next owner / scribe:
* Next owner / scribe: Dave/Matt
* Next week's meeting notes:
* Next week's meeting notes: https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2016-02-11

Latest revision as of 12:07, 5 February 2016

Meeting details

Please see our public calendar for all upcoming events and meetings.

Our regular team meeting occurs every Thursday @ 9am Pacific

Lead / Scribe

  • Lead: Bob
  • Scribe: Madalin
    • Scribe is responsible for:
      • adding the action items and takeaways to the current meeting's minutes
      • creating the agenda for the next meeting and carrying the action items and takeaways over to it
      • sending out a notice of the availability of that agenda along with the meeting invite
      • completing all of the above by the end of the week during which the meeting occurred

Last week's action items

  • [CARRY OVER] [kthiessen] Try to update the default version of Appium we use to 1.4.16
  • [CARRY OVER] [stephend] Finalize the "year in review" blog post
  • [CARRY OVER] [mbrandt] Upgrade Selenium with help from [davehunt]
  • [NEW] [sphilip] Create a Q1 Goals page

Read-only

Discussion items

  • [davehunt] I'm going to start updating our test suites to pytest 2.8.7 with pytest-xdist 1.14 and pytest-rerunfailures 1.0.1 (where used).
    • Once complete, I will remove our infrastructure requirements as these will be redundant.
  • [sphilp] meeting format/needs

Goals Check-in - 1st and 3rd meetings, monthly

Blog Ideas

Have ideas you want to blog about, or you think would make interesting topics? Note them here! this is a template, so update here please

Lightning talks

  • [bsilverberg] One and Done / react.js - Search demo #2

Project status / goals for next week (keep it brief)

  • High-priority/supported projects:
    • Marketplace / AMO
    • MDN
    • Mozilla.org
    • MozTrap
    • One and Done
    • Socorro
    • SUMO
  • Available for ownership:
    • Webmaker
    • REMO/Mozilla Reps
    • Wiki

CI updates

If you've worked on Jenkins or Selenium Grid in the last week, add the necessary info in the Wiki

Community update

Time off / Out-of-office

PTO and other time out of office for Firefox Test Engineering

  • [davehunt] - October 26 - PTO
  • [davehunt] - December 12-14 - Honolulu marathon

Buildmaster (2-week duration)

  • Hands off to the next person at the end of the current Buildmaster's 2-week role, in the Web QA Thursday meeting

Rotation

The Web QA Buildmaster Rotation page contains the past and upcoming schedule.

These entries are in reverse chronological order.

  • 2016-05-05 - 2016-05-19 - stephend
  • 2016-04-21 - 2016-05-05 - mbrandt
  • 2016-04-07 - 2016-04-21 - davehunt
  • 2016-03-24 - 2016-04-07 - rbillings
  • 2016-03-10 - 2016-03-24 - krupa

Action items

  • [CARRY OVER] [kthiessen] Try to update the default version of Appium we use to 1.4.16
  • [CARRY OVER] [stephend] Finalize the "year in review" blog post
  • [NEW] [davehunt] Start updating all our suites to the latest pytest
  • [DONE] [davehunt] Add moving our suites into the developer workflow to the baseline.

Next Meeting

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Execution/Web_Testing/Meetings/2016-02-04&oldid=1116026"