Confirmed users
1,504
edits
QA/Execution/Web Testing/Meetings/2012-04-05: Difference between revisions
Jump to navigation
Jump to search
QA/Execution/Web Testing/Meetings/2012-04-05 (view source)
Revision as of 17:44, 5 April 2012
, 5 April 2012→Discussion Items / Updates
| Line 29: | Line 29: | ||
** Brainstorm them here: https://mozqa.etherpad.mozilla.org/mozwebqa-Q22012-Goals | ** Brainstorm them here: https://mozqa.etherpad.mozilla.org/mozwebqa-Q22012-Goals | ||
*** WebDev's Q2 draft goals: https://etherpad.mozilla.org/webdev-q2-2012 | *** WebDev's Q2 draft goals: https://etherpad.mozilla.org/webdev-q2-2012 | ||
*** Start filling out https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2012/Q2 | *** Start filling out https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals | ||
/2012/Q2 | |||
*** Stephend did look at goals, need to add airmozilla & engagement projects [list has been updated]. Apps will be added also. Want to give what we have to Bob and get his reaction before putting more. Can meet if we want to discuss more- ideally after Bob looks at what we have. We're aiming to go for cautious rather than ambitious. Bob doesn't want normal work as a goal, he also doesn't want goals you don't think you'll meet. | |||
* Jenkins Backup | * Jenkins Backup | ||
** The basic restore procedure has been documented here https://wiki.mozilla.org/QA/Execution/Web_Testing/Automation/Selenium_Grid#Jenkins_Backup | ** The basic restore procedure has been documented here https://wiki.mozilla.org/QA/Execution/Web_Testing/Automation/Selenium_Grid#Jenkins_Backup | ||
*** Dave is contributing some ideas to the awkward step of restoring the plugins. | *** Dave is contributing some ideas to the awkward step of restoring the plugins. | ||
*** Zac: A couple of steps might change to make it more robust. We now have a daily backup and steps for restoring Jenkins. Task completed! | |||
* Project coverage | * Project coverage | ||
** Selenium Conf participants | ** Selenium Conf participants - if you need coverage for a project during the conference let the team know. | ||
* Automation project coverage discussion: | |||
**Right now the onus of fixing a project is on the project lead, even if they are in a diff time zone. Need to balance this out in a way similar to the engagement projects. Don't want a prescriptive thing, but need a method to provide coverage by those available when project leads are offline. Reason: there was a flightdeck push with a failure. It was a prob relating to code and they wanted to know about the flightdeck tests and no one was familiar with them. Would like to see some discussions on this. | |||
** we have a need for people, esp. in Mtn View timezone who can watch & fix failing tests. Lots of coverage in Europe. It seems like on Mtn View side there is so much going on it's hard to consistently keep an eye on the build while planning new tests, going to meetings, etc. A suggestion on the AMO side was having a rotation for someone who only pays attention to the build during certain periods of time. It could allow someone to focus on the builds without having divided attention. | |||
** This was easier when there were fewer projects. Everyone is having more projects and more meetings. | |||
** Could encourage devs to really take a look at tests. People like jsocol and other devs are really interested in looking at our tests. | |||
** Some of our projects it'll require a cultural change, which is a positive direction- sounds like the right path to go down [to have devs help] | |||
** Devs have offered in the past to help. | |||
** marlenac: I know I have an action item to talk to addon devs about this. There are probably other opportunities to do this on other projects. | |||
= Engagement Project Status = | = Engagement Project Status = | ||