> To me, checking whether the attribute changed is more straight-forward
> than implementing a custom matcher, at least at my current level of
> experience (novice) with rails and rspec.
Okay, so that didn't last very long. Suddenly, I was swimming in very
repetitive code in my _spec files...I cou
I failed to mention I'm using Rails 2.3.8 and Rspec-1.3.x. I should
have said that right away.
On Tue, Nov 2, 2010 at 01:33, Alexey Ilyichev wrote:
> An attempt to assign protected attributes leads to the warning in your log
Hmm... Maybe I should actually look at the log once in a while...
>
I've been puzzling over how to test that attr_accessible has been set
for the correct columns; but the tests I've come up with so far seem
to fail to fail when I expect. I came across this old message from
this list:
http://www.mail-archive.com/rspec-users@rubyforge.org/msg01570.html
Which seemed