When first learning how to write tests for rails applications (or anything for that matter), using RSpec, probably my biggest stumbling block, was mocking and testing my controllers. There was just so much to take in it was hard to make sense of it all. But, little by little I made progress. In this article I'll go over writing some basic tests for your controller and offer some of the methods you can use to write your tests.
Teachmate.org has open up it's doors and made the website's code opensource. Teachmate is about offering your knowledge to become and online teacher and/or to find people who would be willing to train you in a particular field, check it out: Teachmate. As far as I'm aware, this is one of the few actual websites where they have made their code opensource - this can only be a good thing for the web community! I found this through the ruby on rails google group.
This is part of a 4-part series which will go over the various tests you can write for your models, controllers, views and acceptance using RSpec. My first article will begin with our application models and testing with and without database connectivity.
It's a rather convoluted way of getting a blog going, but in an attempt to learn more about web infrastructure and environments, I now own my own server, configured it for web requests and setup Ruby on Rails, along with related software, all just to get Mephisto running. And I'm not done there. This box will now be used for all my personal projects, including running as a UAT/Systest box for my more commercial projects. This is also my first blog post here and will most certainly not be the last, as I write about my frustrations and victories in learning new and wonderful technologies (and some old), as well as tutorials and articles regarding PHP, Ruby, Rails and setting up a web server.
