Hello community,
here is the log from the commit of package perl-Test-Object for openSUSE:Factory
checked in at Tue Nov 30 17:54:03 CET 2010.
--------
New Changes file:
--- /dev/null 2010-07-09 01:59:37.000000000 +0200
+++ perl-Test-Object/perl-Test-Object.changes 2010-11-24 22:55:29.000000000 +0100
@@ -0,0 +1,23 @@
+-------------------------------------------------------------------
+Mon Nov 22 14:06:33 UTC 2010 - chris@computersalat.de
+
+- recreated by cpanspec 1.78
+ o fix deps
+- changelog to changes file
+
+-------------------------------------------------------------------
+Tue Oct 19 08:39:08 UTC 2010 - coolo@novell.com
+
+- add perl as explicit buildrequire
+
+-------------------------------------------------------------------
+Wed Oct 21 16:31:28 CEST 2009 - rschweikert@novell.com
+
+- Add changes file
+- Add %dir directive for directories in %files
+- Changelog clean up to only contain initial creation
+
+-------------------------------------------------------------------
+Wed Oct 14 19:00:29 UTC 2009 - rschweikert@novell.com
+
+- Initial build 0.07
calling whatdependson for head-i586
New:
----
Test-Object-0.07.tar.bz2
perl-Test-Object.changes
perl-Test-Object.spec
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ perl-Test-Object.spec ++++++
#
# spec file for package perl-Test-Object (Version 0.07)
#
# 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
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.
# Please submit bugfixes or comments via http://bugs.opensuse.org/
#
# norootforbuild
Name: perl-Test-Object
%define cpan_name Test-Object
Summary: Thoroughly testing objects via registered handlers
Version: 0.07
Release: 1
License: GPL+ or Artistic
Group: Development/Libraries/Perl
Url: http://search.cpan.org/dist/Test-Object/
#Source: http://www.cpan.org/authors/id/A/AD/ADAMK/Test-Object-0.07.tar.gz
Source: %{cpan_name}-%{version}.tar.bz2
BuildArch: noarch
BuildRoot: %{_tmppath}/%{name}-%{version}-build
BuildRequires: perl
%if 0%{?suse_version} < 1120
BuildRequires: perl-macros
%endif
BuildRequires: perl(Carp)
BuildRequires: perl(Exporter)
BuildRequires: perl(File::Spec) >= 0.80
BuildRequires: perl(overload)
BuildRequires: perl(Scalar::Util) >= 1.16
BuildRequires: perl(Test::More) >= 0.42
#
Requires: perl = %{perl_version}
Requires: perl(Carp)
Requires: perl(Exporter)
Requires: perl(File::Spec) >= 0.80
Requires: perl(overload)
Requires: perl(Scalar::Util) >= 1.16
Requires: perl(Test::More) >= 0.42
%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