Confirmed users
9,511
edits
QA/Execution/Web Testing/Meetings/2011-11-17: Difference between revisions
QA/Execution/Web Testing/Meetings/2011-11-17 (view source)
Revision as of 18:06, 17 November 2011
, 17 November 2011→Takeaways and Action Items
| (26 intermediate revisions by 9 users not shown) | |||
| Line 11: | Line 11: | ||
*Marlena to file bugs to get VMWare Fusion licenses for 3,4,5,6 machines (VMWare Fusion 4) | *Marlena to file bugs to get VMWare Fusion licenses for 3,4,5,6 machines (VMWare Fusion 4) | ||
**Start with Windows 7 | **Start with Windows 7 | ||
*Pick a build and run it on Beta | *Pick a build and run it on Beta | ||
*Update betas as soon as they come out | **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 | *Update and use nightlies | ||
**Ditto | |||
= Discussion Items / Updates = | = 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) :-) | |||
* 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?: | |||
**http://www.slideshare.net/wadekar/b-h-a-g1 | |||
**http://www.sitepoint.com/how-to-create-a-big-hairy-audacious-goal/ | |||
***Brainstorm notes, here: https://etherpad.mozilla.org/webqa-bhags | |||
= Project Status / goals for next week (keep it brief) = | = Project Status / goals for next week (keep it brief) = | ||
* | *Affiliates | ||
**Slipped this weeks release due to [https://bugzilla.mozilla.org/show_bug.cgi?id=702465 bug 702465] and [https://bugzilla.mozilla.org/show_bug.cgi?id=703285 bug 703285] | |||
* | *AMO | ||
**[http://cl.ly/0n1A3j2r0a2S0W3R1Z0N 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. | |||
*Input | **We have webdriver jobs in jenkins | ||
**Production run is pending agreement on a production tag | |||
*Jetpack Builder (aka FlightDeck)<br> | **Found critical bug for webdriver in Firefox. It's in the queue to be triaged. | ||
**In the middle of refreshing vms | |||
*Mozilla.com<br> | *Input | ||
**Still in a holding pattern. The entire team is busy doing working Mozillians | |||
*Jetpack Builder (aka FlightDeck)<br> | |||
*Mozillians | **No news but devs asked for some coverage which we should aim to complete in the next week. | ||
** Code Freeze on 11/30 for 1.2 | *Mozilla.com<br> | ||
*Mozillians | |||
*MDN<br> | **Code Freeze on 11/30 for 1.2 | ||
** Working on 1.6 and 1.6.1 [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=mdn14&list_id=1717365 links] | **1.1.2 release | ||
*MDN<br> | |||
* | **Working on 1.6 and 1.6.1 [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=mdn14&list_id=1717365 links] | ||
*Socorro | |||
*SUMO | **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. | |||
*Case Conductor | *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 = | = 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 = | = Takeaways and Action Items = | ||
*Next meeting: | *Next meeting: https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2011-12-01 | ||
*Chair: <br> | *Chair: Stephen | ||
<br> | |||
*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 | |||