Skip to content
shuoman edited this page Nov 18, 2010 · 1 revision

TEST BEFORE SUBMITTING ANYTHING TO GITHUB, DO NOT BREAK THE CODE.

  1. 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

  2. Make beautiful code that passes all rspec tests.

  3. Make sure your code is commented.

  4. Test your program quickly in the UI. Comment your findings in the Issue tracker OR close the issue with comments about it.

  5. The QA manager is happy and can focus on writing tests and designing later acceptance testing and usability testing.