File: control

package info (click to toggle)
libtest-base-perl 0.54-1
  • links: PTS, VCS
  • area: main
  • in suites: lenny
  • size: 620 kB
  • ctags: 174
  • sloc: perl: 1,718; makefile: 15
file content (45 lines) | stat: -rw-r--r-- 2,387 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Source: libtest-base-perl
Section: perl
Priority: optional
Build-Depends: debhelper (>= 7)
Build-Depends-Indep: perl (>= 5.6), libspiffy-perl (>= 0.30),
 libtest-simple-perl (>= 0.62), libalgorithm-diff-perl, libtext-diff-perl,
 libyaml-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: Florian Ragwitz <rafl@debian.org>, Damyan Ivanov <dmn@debian.org>
Standards-Version: 3.8.0
Homepage: http://search.cpan.org/dist/Test-Base/
Vcs-Svn: svn://svn.debian.org/pkg-perl/trunk/libtest-base-perl/
Vcs-Browser: http://svn.debian.org/wsvn/pkg-perl/trunk/libtest-base-perl/

Package: libtest-base-perl
Architecture: all
Depends: ${perl:Depends}, libspiffy-perl (>= 0.30), libalgorithm-diff-perl, libtext-diff-perl, libtest-simple-perl (>= 0.6.2)
Description: A 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.