diff --git a/Test-Routine-0.020.tar.gz b/Test-Routine-0.020.tar.gz deleted file mode 100644 index f66753a..0000000 --- a/Test-Routine-0.020.tar.gz +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db5cfbbb2eb49db336957a5131401b9fbbaec5638141f28f3004d037a888e566 -size 34801 diff --git a/Test-Routine-0.023.tar.gz b/Test-Routine-0.023.tar.gz new file mode 100644 index 0000000..bd03752 --- /dev/null +++ b/Test-Routine-0.023.tar.gz @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8bfc499b038ed68d0bf61248ec343e5a84607f896d1848ed94d6cda56eb0436 +size 37159 diff --git a/cpanspec.yml b/cpanspec.yml new file mode 100644 index 0000000..76ad4a4 --- /dev/null +++ b/cpanspec.yml @@ -0,0 +1,28 @@ +--- +#description_paragraphs: 3 +#description: |- +# override description from CPAN +#summary: override summary from CPAN +#no_testing: broken upstream +#sources: +# - source1 +# - source2 +#patches: +# foo.patch: -p1 +# bar.patch: +#preamble: |- +# BuildRequires: gcc-c++ +#post_prep: |- +# hunspell=`pkg-config --libs hunspell | sed -e 's,-l,,; s, *,,g'` +# sed -i -e "s,hunspell-X,$hunspell," t/00-prereq.t Makefile.PL +#post_build: |- +# rm unused.files +#post_install: |- +# sed on %{name}.files +#license: SUSE-NonFree +#skip_noarch: 1 +#custom_build: |- +#./Build build flags=%{?_smp_mflags} --myflag +#custom_test: |- +#startserver && make test +#ignore_requires: Bizarre::Module diff --git a/perl-Test-Routine.changes b/perl-Test-Routine.changes index fecfac3..a8bfee1 100644 --- a/perl-Test-Routine.changes +++ b/perl-Test-Routine.changes @@ -1,3 +1,26 @@ +------------------------------------------------------------------- +Tue Nov 29 07:20:26 UTC 2016 - coolo@suse.com + +- updated to 0.023 + see /usr/share/doc/packages/perl-Test-Routine/Changes + + 0.023 2016-11-28 17:41:32+11:00 Australia/Melbourne + - When running subtests, use Test2::API rather than Test::More. + This means that Test::Routine tests that never use Test::Builder for + their own testing won't load it at all, but it also means that you'll + need to be on a pretty recent Test-Simple distribution. + - (no code changes from 0.022, just a non-trial release) + + 0.022 2016-07-18 20:13:38-04:00 America/New_York (TRIAL RELEASE) + - fix the mxms.t tests for Test2 changes (really, we should update the + tests to use an event-intercepting hub for our tests) + + 0.021 2016-07-18 12:45:57-04:00 America/New_York (TRIAL RELEASE) + - When running subtests, use Test2::API rather than Test::More. + This means that Test::Routine tests that never use Test::Builder for + their own testing won't load it at all, but it also means that you'll + need to be on a pretty recent Test-Simple distribution. + ------------------------------------------------------------------- Tue Apr 14 19:56:36 UTC 2015 - coolo@suse.com diff --git a/perl-Test-Routine.spec b/perl-Test-Routine.spec index 259a0c6..01c9f16 100644 --- a/perl-Test-Routine.spec +++ b/perl-Test-Routine.spec @@ -1,7 +1,7 @@ # # spec file for package perl-Test-Routine # -# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany. +# Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -17,14 +17,15 @@ Name: perl-Test-Routine -Version: 0.020 +Version: 0.023 Release: 0 %define cpan_name Test-Routine -Summary: composable units of assertion +Summary: Composable Units of Assertion License: Artistic-1.0 or GPL-1.0+ Group: Development/Libraries/Perl Url: http://search.cpan.org/dist/Test-Routine/ -Source: http://www.cpan.org/authors/id/R/RJ/RJBS/%{cpan_name}-%{version}.tar.gz +Source0: http://www.cpan.org/authors/id/R/RJ/RJBS/%{cpan_name}-%{version}.tar.gz +Source1: cpanspec.yml BuildArch: noarch BuildRoot: %{_tmppath}/%{name}-%{version}-build BuildRequires: perl @@ -40,6 +41,7 @@ BuildRequires: perl(Moose::Util::TypeConstraints) BuildRequires: perl(Params::Util) BuildRequires: perl(Sub::Exporter) BuildRequires: perl(Sub::Exporter::Util) +BuildRequires: perl(Test2::API) >= 1.302045 BuildRequires: perl(Test::Fatal) BuildRequires: perl(Test::Moose) BuildRequires: perl(Test::More) >= 0.96 @@ -57,6 +59,7 @@ Requires: perl(Moose::Util::TypeConstraints) Requires: perl(Params::Util) Requires: perl(Sub::Exporter) Requires: perl(Sub::Exporter::Util) +Requires: perl(Test2::API) >= 1.302045 Requires: perl(Test::More) >= 0.96 Requires: perl(Try::Tiny) Requires: perl(namespace::autoclean) @@ -67,23 +70,22 @@ Requires: perl(namespace::clean) Test::Routine is a very simple framework for writing your tests as composable units of assertion. In other words: roles. -For a walkthrough of tests written with Test::Routine, see the -Test::Routine::Manual::Demo manpage. +For a walkthrough of tests written with Test::Routine, see +Test::Routine::Manual::Demo. -Test::Routine is similar to the Test::Class manpage in some ways. These -similarities are largely superficial, but the idea of "tests bound together -in reusable units" is a useful one to understand when coming to -Test::Routine. If you are already familiar with Test::Class, it is the -differences rather than the similarities that will be more important to -understand. If you are not familiar with Test::Class, there is no need to -understand it prior to using Test::Routine. +Test::Routine is similar to Test::Class in some ways. These similarities +are largely superficial, but the idea of "tests bound together in reusable +units" is a useful one to understand when coming to Test::Routine. If you +are already familiar with Test::Class, it is the differences rather than +the similarities that will be more important to understand. If you are not +familiar with Test::Class, there is no need to understand it prior to using +Test::Routine. -On the other hand, an understanding of the basics of the Moose manpage is -absolutely essential. Test::Routine composes tests from Moose classes, -roles, and attributes. Without an understanding of those, you will not be -able to use Test::Routine. The the Moose::Manual manpage is an excellent -resource for learning Moose, and has links to other online tutorials and -documentation. +On the other hand, an understanding of the basics of Moose is absolutely +essential. Test::Routine composes tests from Moose classes, roles, and +attributes. Without an understanding of those, you will not be able to use +Test::Routine. The Moose::Manual is an excellent resource for learning +Moose, and has links to other online tutorials and documentation. %prep %setup -q -n %{cpan_name}-%{version}