rpm/perl-Test-Base
SHA256
1
0
Fork 0
forked from pool/perl-Test-Base
Code Pull Requests Activity

- updated to 0.60

Browse Source 
- Applied patch by andk++
  - Make regexp test skip on 5.14 for now.

OBS-URL: https://build.opensuse.org/package/show/devel:languages:perl/perl-Test-Base?expand=0&rev=18
This commit is contained in:
Stephan Kulow 2011-04-06 11:49:01 +00:00 committed by Git OBS Bridge
parent 1537672d42
commit a079258770
4 changed files with 47 additions and 44 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Test-Base-0.59.tar.bz2
View File

@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:1b6a3efbbd1203bd00fae66418c6355444b30be183f338e3eb8939fceb7bcd42
size 44614

3
Test-Base-0.60.tar.gz Normal file
View File

@ -0,0 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:7d09a9da86dd86b0565f07db01df62593b480db7c1761cb4fabd20af2c18c079
size 60322

7
perl-Test-Base.changes
View File

@ -1,3 +1,10 @@
-------------------------------------------------------------------
Wed Apr 6 10:47:23 UTC 2011 - coolo@novell.com
- updated to 0.60
- Applied patch by andk++
- Make regexp test skip on 5.14 for now.
-------------------------------------------------------------------
Wed Mar 16 12:42:29 UTC 2011 - cfarrell@novell.com

78
perl-Test-Base.spec
View File

@ -1,7 +1,7 @@
#
# spec file for package perl-Test-Base
# spec file for package perl-Test-Base (Version 0.60)
#
# Copyright (c) 2011 SUSE LINUX Products GmbH, Nuernberg, Germany.
# Copyright (c) 2010 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
@ -15,64 +15,61 @@
# Please submit bugfixes or comments via http://bugs.opensuse.org/
#
# norootforbuild
Name: perl-Test-Base
%define cpan_name %( echo %{name} | %{__sed} -e 's,perl-,,' )
Summary: A Data Driven Testing Framework
Version: 0.59
Release: 12
Version: 0.60
Release: 1
License: GPL+ or Artistic
%define cpan_name Test-Base
Summary: A Data Driven Testing Framework
Url: http://search.cpan.org/dist/Test-Base/
Group: Development/Libraries/Perl
Url: http://search.cpan.org/dist/Test-Base
Source: %{cpan_name}-%{version}.tar.bz2
#Source: http://www.cpan.org/authors/id/I/IN/INGY/Test-Base-%{version}.tar.gz
Source: %{cpan_name}-%{version}.tar.gz
BuildArch: noarch
BuildRoot: %{_tmppath}/%{name}-%{version}-build
%{perl_requires}
#!BuildIgnore: perl-Test-Base
BuildRequires: perl
BuildRequires: perl-macros
BuildRequires: perl(Test::More) >= 0.62
#
BuildRequires: perl(Algorithm::Diff) >= 1.15
BuildRequires: perl(Spiffy) >= 0.30
BuildRequires: perl(Test::Deep)
BuildRequires: perl(Text::Diff) >= 0.35
BuildRequires: perl(YAML)
Requires: perl(Algorithm::Diff) >= 1.15
Requires: perl(LWP::Simple)
Requires: perl(Spiffy) >= 0.30
Requires: perl(Test::Deep)
Requires: perl(Text::Diff) >= 0.35
Requires: perl(YAML)
Provides: %{cpan_name}
%{perl_requires}
%description
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.
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:
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.
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.
Author: Brian Ingerson <INGY@cpan.org>
'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.
%prep
%setup -q -n %{cpan_name}-%{version}
%build
perl Makefile.PL OPTIMIZE="$RPM_OPT_FLAGS -Wall"
%{__perl} Makefile.PL INSTALLDIRS=vendor
%{__make} %{?_smp_mflags}
%check
@ -83,12 +80,11 @@ perl Makefile.PL OPTIMIZE="$RPM_OPT_FLAGS -Wall"
%perl_process_packlist
%perl_gen_filelist
%clean
%{__rm} -rf $RPM_BUILD_ROOT
%clean
%{__rm} -rf %{buildroot}
%files -f %{name}.files
# normally you only need to check for doc files
%defattr(-,root,root)
%defattr(-,root,root,755)
%doc Changes README
%changelog