원클릭으로
perl-testing
Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots.
Clean Architecture patterns for Android and Kotlin Multiplatform projects -- module structure, dependency rules, UseCases, Repositories, and data layer patterns.
Performance baseline and regression detection -- page performance, API latency, build times, and before/after comparison.
Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold.
Automated visual testing and interaction verification -- smoke tests, interaction tests, visual regression, and accessibility audits using browser automation.
Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
| name | perl-testing |
| description | Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology. |
| origin | ECC |
Comprehensive testing strategies for Perl applications using Test2::V0, Test::More, prove, and TDD methodology.
# Step 1: RED -- Write a failing test
use v5.36;
use Test2::V0;
use Calculator;
subtest 'addition' => sub {
my $calc = Calculator->new;
is($calc->add(2, 3), 5, 'adds two numbers');
};
done_testing;
# Step 2: GREEN -- Write minimal implementation
# Step 3: REFACTOR -- Improve while tests stay green
is(
$user->to_hash,
hash {
field name => 'Alice';
field email => match(qr/\@example\.com$/);
etc();
},
'user has expected fields'
);
like(
dies { divide(10, 0) },
qr/Division by zero/,
'dies on division by zero'
);
ok(lives { divide(10, 2) }, 'division succeeds') or note($@);
is($result, 42, 'returns correct value');
ok($user->is_active, 'user is active');
is_deeply($got, { name => 'Alice' }, 'returns expected structure');
like($error, qr/not found/i, 'error mentions not found');
prove -l t/ # Run all tests
prove -lv t/unit/user.t # Verbose, specific test
prove -lr -j8 t/ # Recursive, parallel
my $mock = Test::MockModule->new('MyApp::API');
$mock->mock(fetch_user => sub { { id => 42, name => 'Mock User' } });
# Mock is restored when $mock goes out of scope
cover -test
cover -report html
Target: 80%+ coverage on business logic.
DO: Follow TDD, use Test2::V0, use subtests, mock external dependencies, name tests clearly.
DON'T: Test implementation details, share state between subtests, skip done_testing, over-mock.