kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

- add p5-Test-Debugger-0.14

Browse source 
Have you ever tried to debug a test script that is failing tests? Without too
many modifications, your test script can generate a log file with information
about each failed test.

You can take your existing test script, and with (hopefully) very little
effort, convert it to use Test::Debugger. Then re-run your modified test and
view the log file it creates.

WWW: http://search.cpan.org/dist/Test-Debugger/
This commit is contained in:
Yen-Ming Lee 2008-02-16 22:18:28 +00:00
parent f29b59b820
commit 445d4b2811
Notes: svn2git 2021-03-31 03:12:20 +00:00 
svn path=/head/; revision=207407
5 changed files with 39 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
devel/Makefile
View file

@ -1609,6 +1609,7 @@
SUBDIR += p5-Test-ClassAPI
SUBDIR += p5-Test-Cmd
SUBDIR += p5-Test-Data
SUBDIR += p5-Test-Debugger
SUBDIR += p5-Test-Deep
SUBDIR += p5-Test-Dependencies
SUBDIR += p5-Test-Differences

21
devel/p5-Test-Debugger/Makefile Normal file
View file

@ -0,0 +1,21 @@
# New ports collection makefile for: devel/p5-Test-Debugger
# Date created: February 13, 2008
# Whom: Yen-Ming Lee <leeym@FreeBSD.org>
#
# $FreeBSD$
#
PORTNAME= Test-Debugger
PORTVERSION= 0.14
CATEGORIES= devel perl5
MASTER_SITES= CPAN
PKGNAMEPREFIX= p5-
MAINTAINER= leeym@FreeBSD.org
COMMENT= Create Test Scripts which Generate Log Files
PERL_CONFIGURE= yes
MAN3= Test::Debugger.3
.include <bsd.port.mk>

3
devel/p5-Test-Debugger/distinfo Normal file
View file

@ -0,0 +1,3 @@
MD5 (Test-Debugger-0.14.tar.gz) = e0ea66365b947e0bb37171b1d046a89f
SHA256 (Test-Debugger-0.14.tar.gz) = ed8d85a7eb6b597f145907f605b28caa3a40229f9f72939cf5a5111e93d59224
SIZE (Test-Debugger-0.14.tar.gz) = 8965

9
devel/p5-Test-Debugger/pkg-descr Normal file
View file

@ -0,0 +1,9 @@
Have you ever tried to debug a test script that is failing tests? Without too
many modifications, your test script can generate a log file with information
about each failed test.
You can take your existing test script, and with (hopefully) very little
effort, convert it to use Test::Debugger. Then re-run your modified test and
view the log file it creates.
WWW: http://search.cpan.org/dist/Test-Debugger/

5
devel/p5-Test-Debugger/pkg-plist Normal file
View file

@ -0,0 +1,5 @@
%%SITE_PERL%%/Test/Debugger.pm
%%SITE_PERL%%/%%PERL_ARCH%%/auto/Test/Debugger/.packlist
@dirrm %%SITE_PERL%%/%%PERL_ARCH%%/auto/Test/Debugger
@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/auto/Test
@dirrmtry %%SITE_PERL%%/Test