in reply to Re^2: DBD::Mock and DBD-specific attributes
in thread DBD::Mock and DBD-specific attributes

If I am writing unit tests and I've misspelled the name of the attribute, I'd hope that my mistake would get caught.

I'd suggest that any kind of 'is_mocking' attribute would know which attributes that module is supposed to support, and warn you about using unsupported attributes.

  • Comment on Re^3: DBD::Mock and DBD-specific attributes

Replies are listed 'Best First'.
Re^4: DBD::Mock and DBD-specific attributes
by dragonchild (Archbishop) on Aug 17, 2004 at 02:01 UTC
    That's why I would strongly suggest the usage of something like DBD::Mock::mysql and the like. More in another reply in this thread.

    ------
    We are the carpenters and bricklayers of the Information Age.

    Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

    I shouldn't have to say this, but any code, unless otherwise stated, is untested