Wolfgang Kinkeldei

Today, I tried to test a freshly created DB schema using Test::DBIx::Class. Scanning through the documentation was impossible -- it knows far too many options to get captured within a few minutes. But carefully reading the brilliant manual is worth the time spent. Test::DBIx::Class has a lot of options and test-functions tailored especially to the needs of DB-testing.

My primitive schema knows 3 tables: Sensors, Measures and AlarmConditions. Inside my t/ directory, I needed to create only one supplementary file to allow the tests to get coded: a config file t/etc/schema.pl

{
    schema_class => 'Statistics::EasySchema',
    force_drop_table => 1,
    resultsets => [ qw(AlarmCondition Measure Sensor) ],
    connect_info => ['DBI:Pg:dbname=statistics_test', 'user', 'secret'],
}

My tests started using a blank database which was OK for me in this particular situation with a primitive database like this.

My test-script partially looked like that:

use strict;
use warnings;
use Test::More;
use Test::DBIx::Class;


# ensure DB is empty
is Sensor->count, 0, 'no records in sensor table';


# add a sensor
ok my $sensor = Sensor->find_or_create({name => 'erlangen/keller/temperatur'}),
    'find or create sensor';
is_result $sensor;
is_fields [qw(sensor_id name)], $sensor, [1, 'erlangen/keller/temperatur'],
    'sensor fields look good';
is Sensor->count, 1, '1 record in sensor table';

# more test...

done_testing;

How easy things can be by simply using the right module :-)