What Test Environment Setup do Committers Use in the Ruby Community?

Posted by viatropos on Stack Overflow See other posts from Stack Overflow or by viatropos
Published on 2010-05-12T22:31:08Z Indexed on 2010/05/12 22:44 UTC
Read the original article Hit count: 242

Filed under:
|
|
|

Today I am going to get as far as I can setting up my testing environment and workflow. I'm looking for practical advice on how to setup the test environment from you guys who are very passionate and versed in Ruby Testing.

By the end of the day (6am PST?) I would like to be able to:

  1. Type one 1-command to run test suites for ANY project I find on Github.
  2. Run autotest for ANY Github project so I can fork and make TESTABLE contributions.
  3. Build gems from the ground up with Autotest and Shoulda.

For one reason or another, I hardly ever run tests for projects I clone from Github. The major reason is because unless they're using RSpec and have a Rake task to run the tests, I don't see the common pattern behind it all.

I have built 3 or 4 gems writing tests with RSpec, and while I find the DSL fun, it's less than ideal because it just adds another layer/language of methods I have to learn and remember. So I'm going with Shoulda. But this isn't a question about which testing framework to choose.

So the questions are:

  1. What is your, the SO reader and Github project committer, test environment setup using autotest so that whenever you git clone a gem, you can run the tests and autotest-develop them if desired?
  2. What are the guys who are writing the Paperclip Tests and Authlogic Tests doing? What is their setup?

Thanks for the insight. Looking for answers that will make me a more effective tester.

© Stack Overflow or respective owner

Related posts about testing

Related posts about TDD