[Ruby 1.9] Fix broken ip_range unit tests

`assert` is incorrectly used here, since it just tests that the first
argument is `true`, which in Ruby means _any_ object (eg. 0, 1, "", [],
{}) except `false` and `nil`.

Ruby 1.9 is stricter here and checks that the second argument is a
`String` or `Proc`, thus uncovering the bug/typo. `assert_equal` should
be used here instead.
Merge pull request #110 from jamestyj/jamestyj-ip-range-model-test

[Ruby 1.9] Fix broken ip_range unit tests
locate the new network proposal template based on relative path to the Rails app root location
Merge pull request #111 from aabes/pull-req-master-225b7f536ac55cb9ef75c704a50999f331e1a1a3

This looks fine - I'm going accepting the pull and will test as part of my other integration testing.