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

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Meetings
Jump to navigation Jump to search
 
(27 intermediate revisions by 3 users not shown)
Line 19: Line 19:
** Ask project owners to put a link to the GitHub contributors in the README file in each project
** Ask project owners to put a link to the GitHub contributors in the README file in each project
** Stephen to send a link to the work week's Lanyrd tonight
** Stephen to send a link to the work week's Lanyrd tonight
*** http://lanyrd.com/2012/webqa-work-week/
** Override a single RC and Webdriver project to each use Firefox 9, as a test of our Grid issue
** Override a single RC and Webdriver project to each use Firefox 9, as a test of our Grid issue
*** I've done so, and it doesn't appear to be Firefox 9 or RC/Webdriver-specific (but needs more investigation, clearly)
**** https://etherpad.mozilla.org/webqa-selenium-issues
* Stephen to talk to Bob about having Softvision work on Engagement projects
* Stephen to talk to Bob about having Softvision work on Engagement projects
* Next owner:  
* Next owner:  
* Next week's meeting notes: https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2012-02-02
* Next week's meeting notes: https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2012-02-09


= Discussion Items / Updates =
= Discussion Items / Updates =
* Sergey, do you mind if we move https://github.com/stupchiy/marketing-project-template into the /mozilla/ account?
* Please help moderate/test during tomorrow's Firefox 11 beta 1 testday: https://etherpad.mozilla.org/testday-20120203
* WebQA live test day scheduled for 23rd February (during the work week).
* WebQA live test day scheduled for 23rd February (during the work week).
** We need to create a list of tasks/activities. Please add to https://etherpad.mozilla.org/mozwebqa-q1workweek
** We need to create a list of tasks/activities. Please add to https://etherpad.mozilla.org/mozwebqa-q1workweek
Line 31: Line 36:
* New projects:
* New projects:
** ReMo: https://wiki.mozilla.org/ReMo/Website
** ReMo: https://wiki.mozilla.org/ReMo/Website
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=722518 QA review bug]
** Firefox Flicks: https://wiki.mozilla.org/Websites/Firefox_Flicks
** Firefox Flicks: https://wiki.mozilla.org/Websites/Firefox_Flicks
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=720938 QA review bug]
* Should we bring qa-sel7 on board?
** To at least replace qa-sel2
* Raymond, mobile Tegra2 board/test-running infrastructure update, please?
* We should try running Firefox Aurora builds (need some installs on some VMs, as well as a few Mac Minis)
* Let's really start executing on goals: https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2012/Q1
* Just updated our Netsparker installation on the VM on qa-sel7 to [http://www.mavitunasecurity.com/blog/announcing-netsparker-21/ 2.1]
* In anticipation of the work week, please also update https://wiki.mozilla.org/QA/Execution/Web_Testing/Automation/ToDo


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


*Engagement projects  
*Engagement projects  
*Affiliate
** Successful push yesterday, [[bug 722478]]
** Rajeev [:rshetty] led the release. Transitioning in as the QA lead on the project.


*AMO
*AMO
** [http://cl.ly/0S2e1H3M402B1s0i2o2s AMo 6.4.0] is going live on 02/03
** [http://cl.ly/0S2e1H3M402B1s0i2o2s AMO 6.4.0] is going live on 02/03
**Paypal Contribution test is merged
**Paypal Contribution test is merged
**MPL2 license is merged
**MPL2 license is merged
Line 50: Line 67:


*Input
*Input
** Project hand-off from mbrandt to zac


*Jetpack Builder (aka FlightDeck)
*Jetpack Builder (aka FlightDeck)
Line 57: Line 75:


*Mozillians
*Mozillians
** Dev is currently blocked by bug xxx


*MDN
*MDN
Line 62: Line 81:


*Socorro
*Socorro
** Successful 2.4.1 milestone released yesterday -  [[bug 723185]]


*SUMO
*SUMO
Line 84: Line 104:
= Takeaways and Action Items =
= Takeaways and Action Items =
* Takeways:
* Takeways:
**
**  
* Action Items:
* Action Items:
**
** Need a pull request to get qa-sel7 on-board
* Next owner:
** Stephen to try to get another Tegra2 from Bob
* Next week's meeting notes:
* Next owner: Rebecca
* Next week's meeting notes: https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2012-02-09

Latest revision as of 21:03, 5 February 2012

previous mtg | QA/Execution/Web Testing/ Web QA Home | next mtg

Every Thursday @ 9am PDT/PST

Dial-in Information:

Please click on the link below to attend: https://v.mozilla.com/flex.html?roomdirect.html&key=ZAlDIwL9AJcf

If you do not have a user account, please enter your name in the "Guest Name" field and then click "Join".

To join from a telephone, dial the following number:

+1 650 903 0800, x92 9303 or +1 800 707 2533, pin 369 - conf 9303

Action Items / Takeaways from Last Week

Discussion Items / Updates

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

  • Engagement projects
  • Affiliate
    • Successful push yesterday, bug 722478
    • Rajeev [:rshetty] led the release. Transitioning in as the QA lead on the project.
  • AMO
    • AMO 6.4.0 is going live on 02/03
    • Paypal Contribution test is merged
    • MPL2 license is merged
    • Marlena had to help out with apps for much of this week.
  • Engagement
    • Careers is blocked on one bug, waiting for ckoehler
    • DTPT Phase II is complete
  • Marketplace
  • Input
    • Project hand-off from mbrandt to zac
  • Jetpack Builder (aka FlightDeck)
  • Mozilla.com
    • shipped bugs for Firefox 10.0 release on 01/31
  • Mozillians
    • Dev is currently blocked by bug xxx
  • MDN
    • shipped milestone 2.1
  • Socorro
    • Successful 2.4.1 milestone released yesterday - bug 723185
  • SUMO
    • 1/31 release went out, 25% of users are currently on Elastic search
    • 2/7 release in process
    • Questions day February 2nd!
  • Case Conductor
    • Working towards feature parity with new django build, aiming for early February

Community Update

  • Meetings are brainstorming ways to get improve Community within our own projects.
  • Big ideas from last meeting:
    • Need to clean up QMO docs for onboarding new users - I mentioned this was a goal in our upcoming work week
    • Ideas about how to thank contributors. Planning on creating blog posts to feature contributors on the front page of QMO. If you have a project with a contributor you want to thank, this is an easy and very cool way to do it.
    • Ideas on making a simple template for advertising short or long term projects on QMO- advertising for volunteers. Outline the project, the timeline, the skills needed- and put it in a 'notecard' format, and then email personally any contributor who downloads it.
    • Please communicate to me [rbillings] any community work you are doing so I can relate it back to the Community team. There is a feeling that many people are doing things in an isolated way, and it'd be great to collate the data.

Time off / Out-of-office

Takeaways and Action Items