While not as good as probably using DBD::Mock, I usually test my Class::DBI based modules through a series of tests using DBD::SQLite since it doesn't rely on MySQL/Postgres/MSSQL installs. Of course, the minute I need db specific SQL, I'm screwed. :-)
Usually, I'll use_ok/isa_ok the modules, load sql schema/data into a db file using DBI, override the Class::DBI::connection/set_db to point to that file, then test all the interactions and results.
Now granted, I'm testing just as much SQLite as I am my module, but the same it true at a certain level for DBD::Mock as well I guess.
-
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.
|
