I’m going through Michael H.'s Rails tutorial, and I am happy to
that (as of the end of section 7) I’m able to get things working. (That
said, I skipped the section on automated testing, as Hartl warned that
automated testing is the most likely part of his book to become
There is a heavy emphasis on the “bundle exec rspec spec” tests. I
that testing is a very necessary part of development. As I go through
rest of this tutorial, I will continue to test when instructed.
That said, how essential are the “bundle exec rspec spec” tests in most
real world apps? My reasons for possibly not using them or not using
as thoroughly as the tutorial does:
- I still feel more comfortable testing by accessing my web site in
browser and trying things out as if I were one of my users.
- Creating the tests does add to the workload.
- Garbage in -> garbage out: If you don’t write the proper tests, your
results don’t matter but could cause you to needlessly obsess over
something that actually works but you erroneously think is in error, or
could think something works when it doesn’t.
After I finish railstutorial.org, I will start my first Ruby on Rails
site, which will profile mutual funds and ETFs. How important is it
do the “bundle exec rspec spec” testing as thoroughly as the tutorial