QA/Execution/Web Testing/Meetings/2015-04-16: Difference between revisions

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Meetings
Jump to navigation Jump to search
 
(6 intermediate revisions by 3 users not shown)
Line 18: Line 18:
**  
**  
* Action Items:
* Action Items:
** [bsilberberg] add buildmaster wiki page to template
** {{done|}}[bsilverberg] add buildmaster wiki page to template
** [davehunt] create git issues for each project that can benefit from upgrading py.test to v 2.7
** {{done|}}[davehunt] create git issues for each project that can benefit from upgrading py.test to v 2.7
*** I also created issues for setting up flake8 checking in Travis-CI, changing existing Travis-CI integration to just flake8 checking, and where appropriate fixing flake8 issues.
** [all-team] discuss - https://wiki.mozilla.org/QA/Execution/Web_Testing/testplans/community_testplan
** [all-team] discuss - https://wiki.mozilla.org/QA/Execution/Web_Testing/testplans/community_testplan
** Carry over until stephend returns - [davehunt] Currently our Macs are running several different OS versions, do we need to be running tests on Mac OS X?
** {{prev|}}[davehunt] Currently our Macs are running several different OS versions, do we need to be running tests on Mac OS X?
 
*** Carry until Stephen is back to discuss.


== Read-only ==
== Read-only ==
Line 29: Line 30:
= Discussion Items / Updates =
= Discussion Items / Updates =
* [mbrandt] consider creating a template community & continuous delivery test plan. Come prepared to discuss - https://wiki.mozilla.org/QA/Execution/Web_Testing/testplans/community_testplan
* [mbrandt] consider creating a template community & continuous delivery test plan. Come prepared to discuss - https://wiki.mozilla.org/QA/Execution/Web_Testing/testplans/community_testplan
** problem to solve: collect best practices, ideas, components, call out similarities in test plans
audience:
us: talk about how we test, get ideas from others, continuous deployment
project
teams: letting others know what we do
community: knowledge transfer, what X means to us, defining roles and components
* [davehunt] discussion of reruns and timeouts for jobs on Jenkins
** new environment variable WEBQA_TIMEOUT added with a value of 60


= [[QA/Goals/2015q1|Goals Check-in]] - 1st and 3rd meetings, monthly =
= [[QA/Goals/2015q1|Goals Check-in]] - 1st and 3rd meetings, monthly =
Line 61: Line 71:
= Time off / Out-of-office  =
= Time off / Out-of-office  =
{{WebQAPTO}}
{{WebQAPTO}}
{{WebQABuildmaster}}


= Takeaways and Action Items =
= Takeaways and Action Items =
* Takeways:
* Takeaways:
**
**
* Action Items:
* Action Items:
**
** {{prev|}}[davehunt] Currently our Macs are running several different OS versions, do we need to be running tests on Mac OS X?
{{WebQABuildmaster}}
*** Carry until Stephen is back to discuss.
 
** {{prev|}}[davehunt]  discussion of reruns and timeouts for jobs on Jenkins
*** new environment variable WEBQA_TIMEOUT added with a value of 60
** [mbrandt] add overview of who the audiences are to the community test plan document
** [rbillings] look at extra "takeaways" area on meeting template
= Next Meeting =
= Next Meeting =
* Next owner / scribe:
* Next owner / scribe: mbrandt/madalina
* Next week's meeting notes:
* Next week's meeting notes:
https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2015-04-23

Latest revision as of 17:51, 16 April 2015

Web QA Home

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:
    • tericharles
  • Scribe:
    • rbillings
    • 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

Action Items / Takeaways from Last Week

  • Takeways:
  • Action Items:
    • [DONE] [bsilverberg] add buildmaster wiki page to template
    • [DONE] [davehunt] create git issues for each project that can benefit from upgrading py.test to v 2.7
      • I also created issues for setting up flake8 checking in Travis-CI, changing existing Travis-CI integration to just flake8 checking, and where appropriate fixing flake8 issues.
    • [all-team] discuss - https://wiki.mozilla.org/QA/Execution/Web_Testing/testplans/community_testplan
    • [CARRY OVER] [davehunt] Currently our Macs are running several different OS versions, do we need to be running tests on Mac OS X?
      • Carry until Stephen is back to discuss.

Read-only

  • Team - Reach out to davehunt with questions regarding upgrading py.test to v 2.7 if you have questions

Discussion Items / Updates

audience: us: talk about how we test, get ideas from others, continuous deployment project teams: letting others know what we do community: knowledge transfer, what X means to us, defining roles and components

  • [davehunt] discussion of reruns and timeouts for jobs on Jenkins
    • new environment variable WEBQA_TIMEOUT added with a value of 60

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

Testdays and Sessions

Warning signWarning: This template is no longer in use. Please directly include the Web QA Events page instead.

The Web QA Events page shows any upcoming meetups, test days, and other events for the team.

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 talk / Show 'n Tell

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

  • High-priority/supported projects:
    • Marketplace / AMO
    • 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

Warning signWarning: This template is no longer in use. Please directly include the Web QA PTO page instead.

PTO and other time out of office for Firefox Test Engineering

  • [davehunt] - October 26 - PTO
  • [davehunt] - December 12-14 - Honolulu marathon
Warning signWarning: This template is no longer in use. Please directly include the Web QA BuildMaster Rotation page instead.

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

Takeaways and Action Items

  • Takeaways:
  • Action Items:
    • [CARRY OVER] [davehunt] Currently our Macs are running several different OS versions, do we need to be running tests on Mac OS X?
      • Carry until Stephen is back to discuss.
    • [CARRY OVER] [davehunt] discussion of reruns and timeouts for jobs on Jenkins
      • new environment variable WEBQA_TIMEOUT added with a value of 60
    • [mbrandt] add overview of who the audiences are to the community test plan document
    • [rbillings] look at extra "takeaways" area on meeting template

Next Meeting

  • Next owner / scribe: mbrandt/madalina
  • Next week's meeting notes:

https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2015-04-23

Retrieved from "https://wiki.allizom.org/index.php?title=QA/Execution/Web_Testing/Meetings/2015-04-16&oldid=1068859"