forked from pool/perl-Test-Object
94 lines
2.9 KiB
RPMSpec
94 lines
2.9 KiB
RPMSpec
|
#
|
||
|
# spec file for package perl-Test-Object (Version 0.07)
|
||
|
#
|
||
|
# Copyright (c) 2009 Novell
|
||
|
# This file and all modifications and additions to the pristine
|
||
|
# package are under the same license as the package itself.
|
||
|
#
|
||
|
# Please submit bugfixes or comments via http://www.suse.de/feedback/
|
||
|
#
|
||
|
|
||
|
# norootforbuild
|
||
|
|
||
|
Name: perl-Test-Object
|
||
|
Version: 0.07
|
||
|
Release: 1
|
||
|
%define cpan_name Test-Object
|
||
|
Provides: %cpan_name
|
||
|
Requires: perl = %{perl_version}
|
||
|
Autoreqprov: on
|
||
|
Group: Development/Libraries/Perl
|
||
|
License: Artistic License, GPL, see package
|
||
|
URL: http://search.cpan.org/~adamk/Test-Object-0.07/lib/Test/Object.pm
|
||
|
Summary: Test::Object - Thoroughly testing objects via registered handlers
|
||
|
Source0: %{cpan_name}-%{version}.tar.gz
|
||
|
BuildArch: noarch
|
||
|
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root
|
||
|
|
||
|
%description
|
||
|
In situations where you have deep trees of classes, there is a common
|
||
|
situation in which you test a module 4 or 5 subclasses down, which
|
||
|
should follow the correct behaviour of not just the subclass, but of all
|
||
|
the parent classes.
|
||
|
|
||
|
This should be done to ensure that the implementation of a subclass has
|
||
|
not somehow "broken" the object's behaviour in a more general sense.
|
||
|
|
||
|
"Test::Object" is a testing package designed to allow you to easily test
|
||
|
what you believe is a valid object against the expected behaviour of all
|
||
|
of the classes in its inheritance tree in one single call.
|
||
|
|
||
|
To do this, you "register" tests (in the form of CODE or function
|
||
|
references) with "Test::Object", with each test associated with a
|
||
|
particular class.
|
||
|
|
||
|
When you call "object_ok" in your test script, "Test::Object" will check
|
||
|
the object against all registered tests. For each class that your object
|
||
|
responds to "$object->isa($class)" for, the appropriate testing function
|
||
|
will be called.
|
||
|
|
||
|
Doing it this way allows adapter objects and other things that respond
|
||
|
to "isa" differently that the default to still be tested against the
|
||
|
classes that it is advertising itself as correctly.
|
||
|
|
||
|
This also means that more than one test might be "counted" for each call
|
||
|
to "object_ok". You should account for this correctly in your expected
|
||
|
test count.
|
||
|
|
||
|
Authors:
|
||
|
Adam Kennedy <adamk@cpan.org>
|
||
|
|
||
|
%prep
|
||
|
%setup -q -n %cpan_name-%{version}
|
||
|
|
||
|
%build
|
||
|
perl Makefile.PL
|
||
|
make
|
||
|
|
||
|
%check
|
||
|
make test
|
||
|
|
||
|
%install
|
||
|
%perl_make_install
|
||
|
%perl_process_packlist
|
||
|
%__rm -f %{buildroot}%{perl_vendorarch}/auto/Test/Object/.packlist
|
||
|
|
||
|
%clean
|
||
|
rm -rf $RPM_BUILD_ROOT
|
||
|
|
||
|
%files
|
||
|
%defattr(-,root,root,-)
|
||
|
%doc Changes LICENSE README
|
||
|
%doc %{_mandir}/man3/*
|
||
|
%dir %{perl_vendorlib}/Test
|
||
|
%dir %{perl_vendorlib}/Test/Object
|
||
|
%{perl_vendorlib}/Test/Object/Test.pm
|
||
|
%{perl_vendorlib}/Test/Object.pm
|
||
|
/var/adm/perl-modules/%{name}
|
||
|
|
||
|
|
||
|
%changelog
|
||
|
* Wed Oct 14 2009 Robert Schweikert <rschweikert@novell.com> - Test-Object
|
||
|
- Initial build.
|
||
|
|