QA/Execution/Web Testing/Meetings/2011-11-17
From MozillaWiki
< QA | Execution | Web Testing | Meetings
previous mtg | QA/Execution/Web Testing/ Web QA Home | next mtg
Every Thursday @ 9am PDT/PST
Dial-in Information:
650-903-0800 or 650-215-1282 x92 Conf# 303 (US/INTL)
1-800-707-2533 (pin 369) Conf# 303 (US)
Contents
Action Items / Takeaways from Last Week
- Marlena to file bugs to get VMWare Fusion licenses for 3,4,5,6 machines (VMWare Fusion 4)
- Start with Windows 7
- Pick a build and run it on Beta
- Don't think we can do this without using Selenium 2.12*
- Update betas as soon as they come out
- See above
- Update and use nightlies
- Ditto
Discussion Items / Updates
- Jenkins job changes
- Disable wipe out workspace
- Find/remove results/pyc files
- Use pip cache
- Upgrade when installing Python packages
- Specifying versions in Python package dependencies
- Should we standardize our use of py.test marks across projects? What should they be?
- My opinion (and it's just that): it's easier to mark @NoProd and do py.test -k-NoProd in your [projectName.prod] build than to mark all tests for their specific environment (most projects ship from trunk/master weekly) - stephend
- Use branches when some tests are only appropriate to certain environments
- Mozilla.com was using this until recently. Need to to discuss why it was changed? Were there issues?
- See Stephen's update (and tentative apology) :-)
- Mozilla.com was using this until recently. Need to to discuss why it was changed? Were there issues?
- http://pypi.python.org/simple/ makes me cry:
- [21:41:33.703] GET http://pypi.python.org/simple/ [HTTP/1.1 500 Internal Server Error 21875ms] - stephend
- Mobile-testing infra update from Raymond?
- Like to have someone answer https://bugzilla.mozilla.org/show_bug.cgi?id=702605#c2, so we can try to move it right along - stephend
- BHAGS -- what do we want WebQA to be/look like/do, in 2012?:
Project Status / goals for next week (keep it brief)
- Affiliates
- Slipped this weeks release due to bug 702465 and bug 703285
- AMO
- AMO 6.3.2 is going live 11/17
- It's been a week of awesome.
- We've got tests in our pull request queue by our awesome new contributor and plans for everyone to spend half a day on code review today/tomorrow.
- We have webdriver jobs in jenkins
- Production run is pending agreement on a production tag
- Found critical bug for webdriver in Firefox. It's in the queue to be triaged.
- In the middle of refreshing vms
- Input
- Still in a holding pattern. The entire team is busy doing working Mozillians
- Jetpack Builder (aka FlightDeck)
- No news but devs asked for some coverage which we should aim to complete in the next week.
- Mozilla.com
- Mozillians
- Code Freeze on 11/30 for 1.2
- 1.1.2 release
- MDN
- Working on 1.6 and 1.6.1 links
- Socorro
- 2.3.3 is going to be released tomorrow,or latest Monday, depending on the release of FF8.0.
- This weeks release was missed due to a miscommunication. Stage wasn't fully updated & QA tested an incompletely patched system.
- SUMO
- 11/17 is the 2nd SUMO Questions day
- 11/15 went out successfully
- 11/22 in process
- Case Conductor
- .7 release, first dogfoodable release is out and up at: caseconductor.allizom.org
Time off / Out-of-office
- Stephen out the 28th and 29th of November
- Matt B out of office the 17th and 18th to meet with test infected folk up in Seattle. I'll be online and reachable via the normal channels when I'm not in meetings.
Takeaways and Action Items
- Next meeting: https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2011-12-01
- Chair: Stephen
- Project leads will update the Jenkins jobs with the new settings
- Continue discussion about versions in Python package dependencies on mailing list until next week
- Continue the discussion on the maillist until the group takes a decision
- Should we use @destructive / @nondestructive marks
- For AMO we will use temporary marks until the final decision
- Projects leads decide if you want to use branches for running test on different environments[production/development]
- Raymond ping Berada from goolge(should we use Hub or Jenkins)
- Comment the blocking bug, make sure it will be handled on the triage meeting
- Add you ideas to the brainstorm notes
- shoot for the stars
- [Stephen]add more info to clarify what BHAG means