Rails application testing, top to bottom
Intro to a mini-series of articles with advice and pointers on practical, pragmatic testing for Ruby on Rails applications, based on my recent WellRailed presentation on the subject.
Archive
January 2015August 2011
June 2011
May 2011
April 2011
July 2010
June 2010
May 2010
March 2010
February 2010
January 2010
December 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
July 2008
June 2008
May 2008
April 2008
February 2008
January 2008
December 2007
November 2007
October 2007
Blog posts in November 2007
Rails testing miniseries part 2: What we want to test
Before we can get stuck into how to test each bit of our application, we need to be clear about what we need to cover.
Rails testing miniseries part 3: MVC testing
In MVC testing we test that each of parts of our application behave. Testing them separately makes our tests faster to write, faster to run, and reduces rework when we make changes to the app. Covers when to write the tests, and Test::Unit vs. RSpec.
Rails testing miniseries part 4: Model testing
For most apps, this is where you get the biggest pay rate of bugs squashed to time spent. What to test, what not to test, and some inflammatory comments about stubbing out too much.
JIT business in Bangkok
Youtube brings us this brill video of ‘just in time business processes’ in a Bangkok market with a train track running through the middle of it.
Wolves can fish!
Cool video, turns out wolves can fish for salmon, not unlike bears.
Mapping news
An interesting day in mapping 2.0 today, with the beta release of the NZ National Broadband Map project, and Google Maps' upgrade to show terrain shading.
Congo
Turns out the Republic of the Congo is not the same country as the Democratic Republic of the Congo… And some disturbing reports from the DRC :/.
Rails testing miniseries part 5: Controller testing
In Rails apps the main intelligence is supposed to live in the model. As a result, testing properly-designed controllers should mostly be just testing that things are glued together correctly; if your app's factored well, it should be simple and quick to do.
Rails testing miniseries part 6: View testing
View testing allows you to test out complicated or critical view code, but has probably the lowest payoff in terms of problems prevented per developer minute spec.