forked from aeolusproject/conductor
-
Notifications
You must be signed in to change notification settings - Fork 0
Testing_holy_grail
Matt Wagner edited this page Oct 25, 2012
·
1 revision
Note: This was copied across from the old wiki without modification. It may be dated.
- Try to converge to 100% unit test coverage
- Write functional tests (in RSpec meaning controller tests) only when you feel you need to test complex controller logic
- Write Cucumber test whenever you need to test more than one controller flow (Integration testing)
- Also using Cucumber for functional test (as substitution for RSpec controller tests) is welcome
- GOLDEN RULE: NEVER EVER BREAK THE BUILD Before you commit run all the tests.
- Before fixing bug prove the presence of bug with test and than fix it.
- Tests are your friend. If you feel that writing test is hard your code is probably too complex (spaghetti code).