perl-testing
Perl Testing Guide
Comprehensive guide for testing Perl code using Test::More, Test::Class, and related modules.
Test::More Basics
The foundation of Perl testing.
Simple Test File
#!/usr/bin/env perl
use strict;
use warnings;
use Test::More;
# Basic assertions
ok(1, 'truth is true');
ok(!0, 'false is not true');
# Equality
is($got, $expected, 'values are equal');
isnt($got, $unexpected, 'values differ');
# String comparison
is($string, 'expected', 'string matches');
like($string, qr/pattern/, 'matches regex');
unlike($string, qr/bad/, 'does not match regex');
# Numeric comparison
cmp_ok($num, '>', 10, 'greater than 10');
cmp_ok($num, '==', 42, 'equals 42');
# Data structures
is_deeply(\@got, \@expected, 'arrays match');
is_deeply(\%got, \%expected, 'hashes match');
done_testing();
Test Planning
# Declare expected test count
use Test::More tests => 5;
# Or count at end
use Test::More;
# ... tests ...
done_testing();
# Skip remaining tests
use Test::More;
# ... tests ...
done_testing(10); # Explicit count
Running Tests
prove Command
# Run all tests in t/
prove
# Verbose output
prove -v
# Run specific test
prove t/basic.t
# Recursive with color
prove -r --color
# With library path
prove -l t/ # Adds lib/ to @INC
# Parallel execution
prove -j4
# Shuffle order
prove --shuffle
Common prove Flags
| Flag | Purpose |
|---|---|
-v |
Verbose TAP output |
-l |
Add lib/ to @INC |
-b |
Add blib/ to @INC |
-r |
Recursive directory search |
-j N |
Run N tests in parallel |
--color |
Colored output |
--shuffle |
Randomize test order |
--state=save |
Save test state |
Test Organization
Directory Structure
project/
├── lib/
│ └── MyApp/
│ ├── Module.pm
│ └── Utils.pm
├── t/
│ ├── 00-compile.t
│ ├── 01-basic.t
│ ├── 02-module.t
│ └── lib/
│ └── Test/
│ └── MyApp.pm
└── xt/
├── author/
│ └── pod.t
└── release/
└── manifest.t
Compile Test (t/00-compile.t)
#!/usr/bin/env perl
use strict;
use warnings;
use Test::More;
use_ok('MyApp::Module');
use_ok('MyApp::Utils');
done_testing();
Test::More Functions
Assertions
# Boolean
ok($condition, $description);
# Equality
is($got, $expected, $desc); # String comparison
isnt($got, $expected, $desc);
cmp_ok($got, $op, $expected, $desc); # Any operator
# Pattern matching
like($got, qr/pattern/, $desc);
unlike($got, qr/pattern/, $desc);
# Data structures
is_deeply($got, $expected, $desc);
# Reference type
isa_ok($obj, 'ClassName');
can_ok($obj, 'method1', 'method2');
# Pass/fail
pass($desc);
fail($desc);
Diagnostics
# Additional output on failure
is($got, $expected, 'test') or diag("Got: $got");
# Always print
note("Debug info: $value");
# Dump structure
use Data::Dumper;
diag(Dumper($complex_structure));
Skipping and TODO
# Skip tests conditionally
SKIP: {
skip "No database connection", 3 unless $db;
ok($db->ping, 'database responds');
is($db->version, '5.7', 'correct version');
ok($db->tables > 0, 'has tables');
}
# Mark tests as TODO
TODO: {
local $TODO = "Feature not implemented";
is(new_feature(), 'expected', 'new feature works');
}
# Skip all tests in file
plan skip_all => 'Module not installed' unless eval { require Optional::Module };
Test::Exception
Test that code dies or lives correctly.
use Test::More;
use Test::Exception;
# Test that code dies
dies_ok { divide(1, 0) } 'division by zero dies';
# Test that code lives
lives_ok { safe_operation() } 'safe operation lives';
# Test specific exception
throws_ok { bad_call() } qr/invalid argument/i, 'throws expected error';
# Test exception type
throws_ok { bad_call() } 'MyApp::Exception', 'throws correct class';
# Combine with return value
lives_and { is(calc(2, 2), 4) } 'calc lives and returns correct value';
done_testing();
Test::Deep
Deep structure comparison with flexibility.
use Test::More;
use Test::Deep;
# Ignore certain values
cmp_deeply(
$got,
{
id => ignore(), # Any value
name => 'test',
created => re(qr/^\d{4}-\d{2}-\d{2}$/), # Pattern match
},
'structure matches'
);
# Bag comparison (order doesn't matter)
cmp_deeply(
\@got,
bag(1, 2, 3), # Same elements, any order
'contains all elements'
);
# Subset matching
cmp_deeply(
$got,
superhashof({ required => 'value' }),
'contains required keys'
);
# Type checking
cmp_deeply(
$data,
{
count => code(sub { $_[0] > 0 }),
items => array_each(isa('MyApp::Item')),
},
'types correct'
);
done_testing();
Test::MockModule
Mock module behavior for isolation.
use Test::More;
use Test::MockModule;
# Mock a module
my $mock = Test::MockModule->new('MyApp::Database');
# Replace a method
$mock->mock('connect', sub { return 'fake_handle' });
# Mock with return value
$mock->mock('fetch', sub { return { id => 1, name => 'test' } });
# Verify mock was called
my $called = 0;
$mock->mock('save', sub { $called++; return 1 });
# Run code under test
my $result = MyApp::Service->new->process();
is($called, 1, 'save was called');
# Restore original
$mock->unmock('connect');
done_testing();
Test::Class
Object-oriented testing with setup/teardown.
package Test::MyApp::User;
use parent 'Test::Class';
use Test::More;
use MyApp::User;
# Run before each test method
sub setup : Test(setup) {
my $self = shift;
$self->{user} = MyApp::User->new(name => 'Test');
}
# Run after each test method
sub teardown : Test(teardown) {
my $self = shift;
$self->{user} = undef;
}
# Test methods
sub test_creation : Test(2) {
my $self = shift;
isa_ok($self->{user}, 'MyApp::User');
is($self->{user}->name, 'Test', 'name is set');
}
sub test_validation : Test(1) {
my $self = shift;
ok($self->{user}->is_valid, 'user is valid');
}
# Run all Test::Class tests
Test::Class->runtests;
Test::Class Runner
#!/usr/bin/env perl
# t/run_all.t
use strict;
use warnings;
use lib 't/lib';
use Test::MyApp::User;
use Test::MyApp::Order;
Test::Class->runtests;
Fixtures and Test Data
Test Data Files
use Path::Tiny;
use JSON::PP;
sub load_fixture {
my ($name) = @_;
my $file = path("t/fixtures/$name.json");
return decode_json($file->slurp_utf8);
}
# In test
my $data = load_fixture('users');
Database Fixtures
use Test::More;
use DBI;
my $dbh;
sub setup_test_db {
$dbh = DBI->connect('dbi:SQLite::memory:', '', '');
$dbh->do('CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT)');
$dbh->do("INSERT INTO users VALUES (1, 'test')");
}
sub teardown_test_db {
$dbh->disconnect if $dbh;
}
# Use in tests
setup_test_db();
# ... run tests ...
teardown_test_db();
Coverage
# Install Devel::Cover
cpanm Devel::Cover
# Run tests with coverage
cover -test
# Generate HTML report
cover -report html
# View report
open cover_db/coverage.html
Additional Resources
Reference Files
- Test Examples - Complete working test files
- Mock Patterns - Common mocking strategies
Related Skills
For modern Perl coding patterns, see the perl-development skill.
More from jamie-bitflight/claude_skills
perl-lint
This skill should be used when the user asks to lint Perl code, run perlcritic, check Perl style, format Perl code, run perltidy, or mentions Perl Critic policies, code formatting, or style checking.
24brainstorming-skill
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or when users request help with ideation, marketing, and strategic planning. Explores user intent, requirements, and design before implementation using 30+ research-validated prompt patterns.
11design-anti-patterns
Enforce anti-AI UI design rules based on the Uncodixfy methodology. Use when generating HTML, CSS, React, Vue, Svelte, or any frontend UI code. Prevents "Codex UI" — the generic AI aesthetic of soft gradients, floating panels, oversized rounded corners, glassmorphism, hero sections in dashboards, and decorative copy. Applies constraints from Linear/Raycast/Stripe/GitHub design philosophy: functional, honest, human-designed interfaces. Triggers on: UI generation, dashboard building, frontend component creation, CSS styling, landing page design, or any task producing visual interface code.
7python3-review
Comprehensive Python code review checking patterns, types, security, and performance. Use when reviewing Python code for quality issues, when auditing code before merge, or when assessing technical debt in a Python codebase.
7hooks-guide
Cross-platform hooks reference for AI coding assistants — Claude Code, GitHub Copilot, Cursor, Windsurf, Amp. Covers hook authoring in Node.js CJS and Python, per-platform event schemas, inline-agent hooks and MCP in agent frontmatter, common JSON I/O, exit codes, best practices, and a fetch script to refresh docs from official sources. Use when writing, reviewing, or debugging hooks for any AI assistant.
7agent-creator
Create high-quality Claude Code agents from scratch or by adapting existing agents as templates. Use when the user wants to create a new agent, modify agent configurations, build specialized subagents, or design agent architectures. Guides through requirements gathering, template selection, and agent file generation following Anthropic best practices (v2.1.63+).
6