libtest-base-perl 0.89-2 source package in Ubuntu

Changelog

libtest-base-perl (0.89-2) unstable; urgency=medium

  [ gregor herrmann ]
  * debian/watch: use uscan version 4.

  [ Debian Janitor ]
  * Set upstream metadata fields: Bug-Submit.
  * Remove obsolete fields Contact, Name from debian/upstream/metadata (already present in machine-readable debian/copyright).
  * Bump debhelper from old 10 to 13.
  * Set debhelper-compat version in Build-Depends.
  * Remove constraints unnecessary since buster

 -- Jelmer Vernooij <email address hidden>  Tue, 06 Dec 2022 16:55:41 +0000

Upload details

Uploaded by:
Debian Perl Group
Uploaded to:
Sid
Original maintainer:
Debian Perl Group
Architectures:
all
Section:
perl
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Noble release universe perl
Mantic release universe perl
Lunar release universe perl

Builds

Lunar: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libtest-base-perl_0.89-2.dsc 2.2 KiB 9029ca110f060594e399949a3530094f05b4cff9d3d13933b73d56e7a6efb09c
libtest-base-perl_0.89.orig.tar.gz 50.9 KiB 2794a1aaaeb1d3a287dd2c7286258663796562f7db9ccc6b424bc4f1de8ad014
libtest-base-perl_0.89-2.debian.tar.xz 4.2 KiB 4f56b5c5bf02c7b52a2bdca76f188a01597ddcd0e650d45cad91674da646ae42

Available diffs

No changes file available.

Binary packages built by this source

libtest-base-perl: data driven testing framework for Perl

 Testing is usually the ugly part of Perl module authoring. Perl gives you a
 standard way to run tests with Test::Harness, and basic testing primitives
 with Test::More. After that you are pretty much on your own to develop a
 testing framework and philosophy. Test::More encourages you to make your own
 framework by subclassing Test::Builder, but that is not trivial.
 .
 Test::Base gives you a way to write your own test framework base class that is
 trivial. In fact it is as simple as two lines:
   package MyTestFramework;
   use Test::Base -Base;
 .
 A module called MyTestFramework.pm containing those two lines, will give all
 the power of Test::More and all the power of Test::Base to every test file
 that uses it. As you build up the capabilities of MyTestFramework, your tests
 will have all of that power as well.
 .
 MyTestFramework becomes a place for you to put all of your reusable testing
 bits. As you write tests, you will see patterns and duplication, and you can
 "upstream" them into MyTestFramework. Of course, you don't have to subclass
 Test::Base at all. You can use it directly in many applications, including
 everywhere you would use Test::More.
 .
 Test::Base concentrates on offering reusable data driven patterns, so that you
 can write tests with a minimum of code. At the heart of all testing you have
 inputs, processes and expected outputs. Test::Base provides some clean ways
 for you to express your input and expected output data, so you can spend your
 time focusing on that rather than your code scaffolding.