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 26: Line 26:
* Specifying versions in Python package dependencies  
* Specifying versions in Python package dependencies  
* Should we standardise our use of py.test marks across projects? What should they be?
* Should we standardise our use of py.test marks across projects? What should they be?
**My opinion: it's easier to mark @NoProd and do py.test -k-NoProd in your [projectName.prod] build than to mark all tests - stephend
**My opinion: 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
* 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?
** Mozilla.com was using this until recently. Need to to discuss why it was changed? Were there issues?

Revision as of 05:38, 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 standardise our use of py.test marks across projects? What should they be?
    • My opinion: 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?

Project Status / goals for next week (keep it brief)

  • Engagement projects
  • Affiliates
  • AMO
  • Input
  • Jetpack Builder (aka FlightDeck)
  • Mozilla.com
  • Mozillians
    • Code Freeze on 11/30 for 1.2
  • MDN
    • Working on 1.6 and 1.6.1 links
  • Socorro
  • 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


Takeaways and Action Items

  • Next meeting:
  • Chair: