Webdev:Meetings:2008-08-21
From MozillaWiki
- Dev cycle changes (carry over from AMO discussion)
- Why are we feeling rushed or behind at code freeze?
- How should we change the cycle?
- morgamic's idea: 10 days dev time, 3 days QA time, push, 2 days planning/down time during/after push, repeat
- Ideas
- Push on a Tuesday instead - so code freeze thursday and push Tuesday instead
- Bugs in there can be very vague, so we should spend more time making things more specific or planning larger bugs into smaller pieces
- Examples - discussions and shadow database traffic - put bugs into small enough pieces so it's realistic to hit them for certain milestones
- Testing
- Need to start writing tests
- Not going to make everyone go back and write tests retro-actively
- However, we should focus more on writing simple tests (installation tests, syntax error checks, acceptance tests) for most of what we do
- Thoughts on how to "enforce" test writing?
- Ideas
- Test suite sucks -- split up between controllers and models and views and sometimes it doesn't even work
- Sometimes you have to use the view to test the controller
- Initial staring into the headlights -- not sure where to write tests for AMO
- We should clarify if we should change to PHPUnit or stay on SimpleTest
- Test suite is large and runs out of memory a lot -- would be nice to not have that many
- Should investigate switching from SimpleTest to PHPUnit
- Jacob
- Test cluster update
- SSO update and discussion
