-
Notifications
You must be signed in to change notification settings - Fork 0
Testing
shuoman edited this page Nov 18, 2010
·
1 revision
TEST BEFORE SUBMITTING ANYTHING TO GITHUB, DO NOT BREAK THE CODE.
-
Specify objects' behavior with Rspec (aka write Rspec tests). https://github.com/rspec/rspec-rails#readme http://blog.davidchelimsky.net/2007/05/14/an-introduction-to-rspec-part-i/ http://rspec.info http://www.lukeredpath.co.uk/blog/developing-a-rails-model-using-bdd-and-rspec-part-1.html http://cheat.errtheblog.com/s/rspec
-
Make beautiful code that passes all rspec tests.
-
Make sure your code is commented.
-
Test your program quickly in the UI. Comment your findings in the Issue tracker OR close the issue with comments about it.
-
The QA manager is happy and can focus on writing tests and designing later acceptance testing and usability testing.