should_require_unique_attributes fix to actually get a unique value
Reported by Joachim Garth | July 27th, 2008 @ 09:19 AM
should_require_unique_attributes does not properly get a unique value for the test. This is even commented in the code. So because exactly this occurred in my tests (the macro choosing a non-unique value and then complaining about it not being unique), I thought up a solution. Not sure if this will work for everybody, however it does work perfectly for me.
Hope this helps, I really like the project!
Comments and changes to this ticket
-
Josh Nichols September 3rd, 2008 @ 10:06 AM
Were you able to isolate this bug occuring in your test? It might be useful to add something to the shoulda test suite to verify this behavior.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Tammer Saleh
Bob Showalter