3,035
edits
No edit summary |
No edit summary |
||
Line 6: | Line 6: | ||
*** Push on a Tuesday instead - so code freeze thursday and push Tuesday instead | *** 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 | *** 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 | * Testing | ||
** Need to start writing tests | ** Need to start writing tests | ||
Line 11: | Line 12: | ||
** However, we should focus more on writing simple tests (installation tests, syntax error checks, acceptance tests) for most of what we do | ** 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? | ** Thoughts on how to "enforce" test writing? | ||
* Jacob | *** 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 | ** Test cluster update | ||
** SSO update and discussion | ** SSO update and discussion |
edits