In my previous post (Spec Behaviour not Implementation) I went on a froth roll about why you should treat controller actions as black boxes. Here I give an all to common example of why this is good and how you can write specs that won’t break at the most trivial change.

Read the rest of this entry

This has been said a lot, and doesn’t really need repeating by someone like me, but, as this is a tips page, I should put it here.

Read the rest of this entry

Tip #26 - Start Small

June 27th, 2008

If you are getting frustrated with RSpec, then you have probably skipped a gradient. Start smaller!

Read the rest of this entry

Sometimes when you need someone to just look over your code and figure out what the heck is going on, you can turn to your best coding friend, this friend sits away in the log directory carefully collecting data waiting for your beck and call…

Read the rest of this entry

This tip is coming to you from a frustrated developer having to read someone else’s specs….

Read the rest of this entry

RSpec Story xhr problem

June 6th, 2008

If you are using RSpec stories (and if you are not, why not?) you might run into this little problem. doing an xhr :post returns ArgumentError: wrong number of arguments (4 for 3)

Read the rest of this entry

If you are using BE DE DE or TE DE DE, then you will get situations in your specs or tests where you want to be able to just create a valid model of another type to test against. This is where factories and builders come in handy.

Read the rest of this entry

ActiveRecord works well when we are saving strings and integers, but what if you want to save a real, live, honest-to-God Ruby OBJECT like a TMail::Mail instance?? Well.. serialize to the rescue!

Read the rest of this entry