[rspec-users] id getting overwritten with 0 when testing

David Chelimsky dchelimsky at gmail.com
Wed Jan 25 16:45:59 EST 2012

On Wed, Jan 25, 2012 at 3:37 PM, David Chelimsky <dchelimsky at gmail.com> wrote:
> On Wed, Jan 25, 2012 at 3:29 PM, Guyren G Howe <gisborne at emailuser.net> wrote:
>> On Jan 25, 2012, at 3:44 AM, Julian Leviston wrote:
>>> Okay so NOW to me it sounds a lot like you're using a non-integer as a primary key which I wouldn't do...
>> I don’t think you’ve tried to write a server app that synchronizes with handheld apps over an unreliable internet connection. UUIDs make things *so* much easier.
>> The decision about the pks is made. Am I understanding from folks here that rspec *won’t work* without integer primary keys? That is a major design flaw, if true.
> RSpec provides a thin wrapper around the testing framework that ships
> with Rails and extends T/U. I'm not sure I understand the problem yet,
> but I'd be really surprised if it's anything RSpec is doing or failing
> to do.
> What versions of RSpec and Rails are you using?

Just looked back at your initial email and see you cited rspec-2.8,
but the way Rails handles incoming params in tests changed in either
3.1 or 3.2 (I have to check). Which rails version specifically?

More information about the rspec-users mailing list