QA/Execution/Web Testing/Meetings/2011-11-17: Difference between revisions

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Meetings
Jump to navigation Jump to search
Line 47: Line 47:
*Mozillians
*Mozillians
** Code Freeze on 11/30 for 1.2
** Code Freeze on 11/30 for 1.2
** 1.1.2 release
*MDN<br>
*MDN<br>
** Working on 1.6 and 1.6.1 [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=mdn14&list_id=1717365 links]
** Working on 1.6 and 1.6.1 [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=mdn14&list_id=1717365 links]
*Socorro
*Socorro
**2.3.3 is going to be released tomorrow,or latest Monday, depending on the release of FF8.0.1
*SUMO
*SUMO
** 11/17 is the 2nd SUMO Questions day
** 11/17 is the 2nd SUMO Questions day

Revision as of 13:39, 17 November 2011

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)

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) :-)
  • http://pypi.python.org/simple/ makes me cry:
  • 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
  • AMO
  • Input
  • Jetpack Builder (aka FlightDeck)
  • 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.1
  • 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

Takeaways and Action Items

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Execution/Web_Testing/Meetings/2011-11-17&oldid=370602"