Monday, September 20, 2010
Ok, now what to do? assert_change is super easy to use, but does it really ensure that the desired action is actually happening? For example:
This example test asserts that the number of User objects in the database has increased by 1. No real guarantee that it was actually the User object we were interested in creating.
Lately I have been trying to be a little more explicit about what is actually happening. It is taking a little while to get used to doing things this way but the results have been satisfying. Here is an example:
This example test asserts that a User object is getting assigned to the @user instance variable and that User object is no longer a new record.
Wednesday, September 8, 2010
It is really easy to get the order of magnitude wrong on a number in code. I had settled into the habit of carefully counting my digits to make sure it was right until one of my co-workers pointed out a neat feature of ruby.
Ruby allows underscores to be inserted into numbers between any two digits. The underscores are purely cosmetic and do not affect the value of the number. This feature allows a developer to use underscores as an accountant might use commas.
3193490646 # standard representation of a number in ruby 3_193_490_646 # same value, much more readable
One less excuse for order of magnitude errors when using ruby.
Thanks to Dallas Reedy for introducing me to this awesome feature of Ruby