Northern Premier Division Insights & football Betting Overview

In today's digital age, social media plays a pivotal role in engaging with fans before, during, and after matches:

• Promotional Content: Teams utilize platforms like Twitter, Instagram, and Facebook to promote upcoming fixtures and share exclusive content with followers.
• pld-linux/perl-Test-Warn<|file_sep|>/perl-Test-Warn.spec # # Conditional build: %bcond_without tests # do not perform "make test" # %define pdir Test %define pnam Warn Summary: Test::Warn - Test code that uses warn() Summary(pl.UTF-8): Test::Warn - testowanie kodu używającego warn() Name: perl-Test-Warn Version: 0.06 Release: 1 # same as perl License: GPL v1+ or Artistic Group: Development/Languages/Perl Source0: http://www.cpan.org/modules/by-module/Test/%{pdir}-%{pnam}-%{version}.tar.gz # Source0-md5: f9ed7c9d230aa80d6f26e4f9a5e79d51 URL: http://search.cpan.org/dist/Test-Warn/ BuildRequires: perl-devel >= 1:5.8.0 BuildRequires: rpm-perlprov >= 4.1-13 BuildRequires: rubygems-devel >= 1:1.2.0 BuildRequires: rubygems-integration >= 0.2-4 BuildRequires: sed >= 4.0 %if %{with tests} BuildRequires: perl-ExtUtils-ParseXS >= 1.14 BuildRequires: perl-Sys-SigAction >= 0.10 BuildRequires: rubygems-rake >= 0.8.7 %endif BuildArch: noarch BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) %description This module allows you test code that uses warn(). It has no external API, but provides some useful subroutines: =over =item * warn_is Compare warn output against expected output. =item * warn_like Like warn_is but compares using regular expressions. =item * warns Expects that some code should produce warnings. =back %description -l pl.UTF-8 Ten moduł pozwala testować kod używający warn(). Nie posiada zewnętrznego API ale dostarcza kilka przydatnych podprogramów: =over =item * warn_is Porównuje wyjście warn() z oczekiwanym wyjściem. =item * warn_like Podobnie jak warn_is ale porównuje wyjście używając wyrażeń regularnych. =item * warns Oczekuje że dany kod powinien wygenerować ostrzeżenia. =back %prep %setup -q -n %{pdir}-%{pnam}-%{version} %build CFLAGS="%{rpmcflags}" %{__perl} Makefile.PL INSTALLDIRS=vendor %{__make} %{?with_tests:%{__make} test} %install rm -rf $RPM_BUILD_ROOT %{__make} install DESTDIR=$RPM_BUILD_ROOT install -d $RPM_BUILD_ROOT{%{ruby_vendorlibdir},%{_bindir}} cp -a lib/Test/Warn/ruby/test_warn.rb $RPM_BUILD_ROOT%{ruby_vendorlibdir} cp lib/Test/Warn/ruby/test_warn $RPM_BUILD_ROOT%{_bindir}/test_warn.rb install test_warn $RPM_BUILD_ROOT{%{_bindir},%{ruby_sitelibdir}/test} # too many unnecessary files created during tests... find $RPM_BUILD_ROOT -name '*.orig' -o -name 't/.packlist' -o -name '*.t' -o -name '*.cover' | xargs rm -f # useless file created by ExtUtils::MakeMaker: rm $RPM_BUILD_ROOT%{perl_archlib}/auto/Test/Warn/Warn.bs # remove .packlist files: find $RPM_BUILD_ROOT%{perl_archlib}/auto/Test/Warn/ $RPM_BUILD_ROOT%{perl_vendorlib}/Test/Warn/ $RPM_BUILD_ROOT%{_bindir} $RPM_BUILD_ROOT%{ruby_sitelibdir}/test -type f -name '.packlist' | xargs rm -f # obsoleted by rubygems package rm $RPM_BUILD_ROOT{%{_bindir},%{ruby_sitelibdir}}/test_warn.rb %clean rm -rf $RPM_BUILD_ROOT %files %defattr(644,root,root,755) %doc Changes README TODO examples/ t/ %attr(755,root,root) %{_bindir}/test_warn.pl %{perl_vendorlib}/Test/Warn.pm # NOTE! This dir is necessary for test_warn.pl: # use lib 't/lib'; # use Test::Warn qw(); # But Test::Warn::Ruby is not needed anymore because it was replaced by gem: # gem install test-warn (and then require 'test/warn') # So I'm not sure if we should remove this dir... # NOTE! This file is needed by test_warn.pl: # use lib 't/lib'; # use Test::Warn qw(); # NOTE! This file is used by test/test_warn.pl: # eval 'exec perl t/test_warn.pl' # NOTE! These files were added by Makefile.PL: # lib/Test/Warn/Ruby.pm lib/Test/Warn/Ruby/x86_64-linux.xs auto/Test/Warn/Ruby/Ruby.bs # auto/Test/Warn/Ruby/Ruby.so # But Test::Warn::Ruby is not needed anymore because it was replaced by gem: # gem install test-warn (and then require 'test/warn') # # TODO maybe remove this dir after some time? # %dir %{perl_archlib}/auto/Test/Warn/ %attr(755,root,root) %{perl_archlib}/auto/Test/Warn/Ruby.so* #%%doc %{perl_archlib}/auto/Test/Warn/Ruby/Ruby.bs* #%%doc %{perl_archlib}/auto/Test/Warn/Ruby/*.orig* #%%doc %{perl_archlib}/auto/Test/Warn/*.orig* #%%files ruby-gems-testwarnrb-missing-testwarnrb-symlinked-to-testwarn-pl-in-rpm-build-root-dir #%%defattr(644,rhelabuser,rhelabuser) #%%ghost %attr(755,rhelabuser,rhelabuser) %{_bindir}/test_warn.rb <|repo_name|>pld-linux/perl-Test-Warn<|file_sep|>/README.md ## About this fork This fork adds support for testing ruby warnings using `Test::Warn`. ruby require 'test/warn' warn_is "foo", "foo" do warnings "foo" end warn_like /foo/, /bar/ do warnings "foo" end warns /foo/ do warnings "foo" end ## About Test::Warn original module This module allows you test code that uses `warn()`. It has no external API but provides some useful subroutines: * `warn_is` Compare `warn` output against expected output. * `warn_like` Like `warn_is` but compares using regular expressions. * `warns` Expects that some code should produce warnings. ## Example usage: perl use Test::More; use Test::Warn; my $stderr; { local *STDERR; open STDERR,'>', $stderr; warn_is "foo", "foo", 'expected warning'; } is($stderr,"foon","expected STDERR"); done_testing(); <|file_sep|>=head1 NAME Test::Warn - Test code that uses warn() =head1 SYNOPSIS use strict; use warnings; use Test::More; use Test::Warn; # first example from documentation (see below) my $stderr; { local *STDERR; open STDERR,'>', $stderr; warn_is "foo", "foo", 'expected warning'; } is($stderr,"foon","expected STDERR"); done_testing(); =head1 DESCRIPTION This module allows you test code that uses warn(). It has no external API but provides some useful subroutines: =over =item * warn_is Compare warn output against expected output. =item * warn_like Like warn_is but compares using regular expressions. =item * warns Expects that some code should produce warnings. =back =head2 Basic usage To capture warnings issued by some code you need first redirect STDERR into some variable: my $stderr; { local *STDERR; open STDERR,'>', $stderr; # ... here you call code you want test ... } The redirection will be automatically removed after block ends so don't forget it! Now you can compare your captured warnings using provided subroutines: # compare captured warning exactly against expected one: # (also check if there were no other warnings) ok(!warnings(),"no unexpected warnings"); ok(warnings(),"we expect at least one warning"); warn_is($stderr,"expected warning","expected warning"); # compare captured warning using regexp: # (also check if there were no other warnings) ok(!warnings(),"no unexpected warnings"); ok(warnings(),"we expect at least one warning"); warn_like($stderr,"expected .* warning","warning contains expected text"); Also you can check if your code produced any warnings: # check if your code produced any warnings: # (this subroutine only check if there were any warnings, # it doesn't compare them against anything) warns(sub { ...your code here... },"at least one warning"); =cut package Test::Warn; use strict; use Carp qw(croak); use Exporter qw(import); use vars qw(@EXPORT_OK); @EXPORT_OK = qw(warn_is warn_like warns); my %warnings = (); BEGIN { my @tests = ( { name => 'ok', subroutine => &ok }, { name => 'is', subroutine => &is }, { name => 'isnt', subroutine => &isnt }, { name => 'like', subroutine => &like }, { name => 'unlike', subroutine => &unlike }, { name => 'cmp_ok', subroutine => &cmp_ok }, { name => 'isa_ok', subroutine => &isa_ok }, { name => 'lives_ok', subroutine => &lives_ok }, { name => 'throws_ok', subroutine => &throws_ok }, { name