This is exactly what DBD::Mock was designed for ... kinda. Chris Winters, then stvn and I, planned DBD::Mock to be for people who use DBI directly. We have only just started playing with Class::DBI ourselves. It may be useful to come up with a way of mocking CDBI itself, because that's the interface you want to test, not DBI's interface. I suggest emailing the CDBI mailing list.

Some quick googling reveals http://www.spanner.org/lists/cdbi/2005/03/05/e66a0853.html, implying that DBD::Mock and CDBI don't work together out of the box, at least in that scenario.

Maybe Class::DBI::Mock needs to be written. I don't think it's a simple thing, though, given the amount of work that goes on behind the scenes in CDBI and how tightly some of it's coupled to other things.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.