All the Perl that's Practical to Extract and Report
use Perl Log In
jplindstrom (594)
(email not shown publicly)
Journal of jplindstrom (594)
Testing, Perl and databases
Found this talk about Perl Testing by Michael Graham.
Useful Test::* modules at the end.
I found the slides when searching for dies_ok, which I was sure I had seen but couldn't find in the man pages for Test::More. And Test::Exception installed without a hitch.
I'm currently writing a test framework for an application server of ours. I'll be using Test::More as the actual framework and perform XML calls to the app server.
The only annoying thing with this is that the app server is only a business logic layer on top of a database, and after/before each run of a test suite, I need to get the database into a consistent state.
The current plan is to keep track of certain tables that actually change and delete from them, then insert default data again.
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
Testing databases. (Score:2)
-Dom
Testing modules (Score:2)
--
xoa
Re:Testing modules (Score:1)
If there is nothing on CPAN, I think I'll write a simple tableRowCount($table) method to get the number of rows in a table. That should be useful for detecting new lines in a table after a call.
Or maybe a row_inserted_ok($table, $number_of_new_rows, $label). Yes... hmmm... that sounds like something... hmmm...
Re:Testing modules (Score:2)
--
xoa