QA/Execution/Web Testing/Meetings/2012-05-31
< QA | Execution | Web Testing | Meetings
Jump to navigation
Jump to search
previous mtg | Web QA Home | next mtg
Meeting Details
Please see our public calendar for all upcoming events and meetings.
Our regular team meeting occurs every Thursday @ 9am Pacific
Action Items / Takeaways from Last Week
- Takeaways:
- Action Items:
Discussion Items / Updates
- amo.prod instance in Phoenix/Jenkins (https://ci.mozilla.org/) -- status?
- Set up job in ci.mozilla.org
- Start hub and node on boot
- Restart hub and node on failure
- Push PHX changes to moz-grid-config
- Clone node VM for running tests in parallel
- Documentation!
- Need help getting the new-user registration flow back up on browserid-tests, against dev.123done.org and beta123done.org, using BIDPOM.
- Should be simple - create staging & production branches for browserid-tests, update BIDPOM in these branches to use the appropriate versions, and update staging & master branches to use new registration flow as shown in the tests.
- Stalled builds are back, and now we have the backup plugin there's a new side-effect: the plugin prepares Jenkins for shutdown before a backup, but waits for all jobs to complete (and enforces 'quiet node' after waiting 2 hours). If there are stalled jobs then Jenkins is essentially doing nothing until the jobs are aborted. I think we may need to investigate using the pytest-timeout plugin, however it currently clashes with pytest-mozwebqa. For now I have re-enabled abort for amo.dev and marketplace.dev.
- After investigating the above, I noticed that the backups were failing. This was due to the drive they are backed up to not being mounted. I have fixed this, but it should be a buildmaster responsibility to ensure backups are successful.
- There seems to still be confusion over implicit/explicit timeouts with WebDriver and Selenium Grid timeouts. The former are important to understand when writing tests. How can we improve this situation?
- How are we doing with investigating performance testing/tools/metrics we need to measure?
Engagement Project Status
If you've worked on an engagement project in the last week, enter your name, the project name, and time spent in hours (estimated).
Project Status / goals for next week (keep it brief)
- Affiliates
- No updates
- AMO
- Marketplace
- Input
- Jetpack Builder (aka FlightDeck)
- Mozilla.com
- Mozillians
- The TaskBoard has been de-prioritized as a goal for this quarter
- The Phonebook: Basecamp goals
- allow users to add geographic location data to their profiles
- enhanced search/filter capabilities: Group, Skill, and Location
- an API for the Phonebook
- the tree is open for commits - the 06-06-2012 train leaves this morning
- MDN
- Socorro
- [upcoming] June 11th Stability Workweek - wkwk agenda - https://etherpad.mozilla.org/StabilityWorkWeek
- Milestone 10 and milestone 10.1 released last week
- Milestone 11 released yesterday
- SUMO
- Continuous deployment, no updates
- MozTrap
- Wiki
Buildmaster
Community Update
Time off / Out-of-office
Takeaways and Action Items
- Takeways:
- Action Items:
- Next owner:
- Next week's meeting notes: