File perl-App-Test-Tapat.spec of Package perl-App-Test-Tapat

#
# spec file for package perl-App-Test-Tapat
#
# 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
# 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/
#


Name:           perl-App-Test-Tapat
Version:        0.04
Release:        0
%define cpan_name App-Test-Tapat
Summary:        An automated testing framework
License:        GPL-1.0+ or Artistic-1.0
Group:          Development/Libraries/Perl
Url:            http://search.cpan.org/dist/App-Test-Tapat/
Source0:        http://www.cpan.org/authors/id/J/JE/JEREMIAH/%{cpan_name}-%{version}.tar.gz
BuildArch:      noarch
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildRequires:  perl
BuildRequires:  perl-macros
BuildRequires:  perl(Moose)
BuildRequires:  perl(TAP::Harness)
BuildRequires:  perl(TAP::Parser)
BuildRequires:  perl(TAP::Parser::Aggregator)
Requires:       perl(Moose)
Requires:       perl(TAP::Harness)
Requires:       perl(TAP::Parser)
Requires:       perl(TAP::Parser::Aggregator)
%{perl_requires}

%description
Tapat aims to be an automated testing framework. It currently only provides
a mechanism to run tests which contain TAP, receive the test's output, and
relay that output further to a report and, in the future, a database.

Tapat is designed to be programming language agnostic. This means that you
can write tests in any language that can produce TAP, and many languages
can, including perl, python, php, bash, C/C++, Java, various SQL
implementations, ruby, and any language that can create simple TAP output.
(See the TAP wiki.) Once your tests are written, they are run by the tapat
harness and reports are created.

The goal is to allow testers to focus on their testing, not the mechanism
or framework that surrounds their tests, enabling a simple drop-in
mechanism for new automated tests to run inside of. So with Tapat, you get
a parsing and reporting layer for your tests.

%prep
%setup -q -n %{cpan_name}-%{version}

%build
%{__perl} Makefile.PL INSTALLDIRS=vendor
%{__make} %{?_smp_mflags}

%check
%{__make} test

%install
%perl_make_install
%perl_process_packlist
%perl_gen_filelist

%files -f %{name}.files
%defattr(-,root,root,755)
%doc Changes README

%changelog