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

Line 25: Line 25:
** Upgrade when installing Python packages
** Upgrade when installing Python packages
* 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 standardize 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
**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
* 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?
***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


= Project Status / goals for next week (keep it brief)  =
= Project Status / goals for next week (keep it brief)  =
Confirmed users
9,511

edits