3,035
edits
mNo edit summary |
No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 3: | Line 3: | ||
** How should we change the cycle? | ** 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 | ** 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 | * Testing | ||
** Need to start writing tests | ** Need to start writing tests | ||
Line 12: | 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? | ||
* Ideas | |||
** Test suite sucks -- split up between controllers and models and views and sometimes it doesn't even work | ** 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 | ** Sometimes you have to use the view to test the controller |
edits