Hi Scott,
I am part of the Debian Perl Group, and have just packaged the
Test::FITesque CPAN module for release.
Thanks for releasing your work to the CPAN, and I apologise in advance for
this noise.
In packaging software we perform various checks on the software, out of
which I found a number of spelling errors.
The above patch shows the spelling errors I found in packaging v0.04, and
suggested corrections therein.
Feel free to respond to this email.
Regards
--
Ken Ibbotson
E: k...@computer.org
*"Reality is merely an illusion, albeit a very persistent one."*
- Albert Einstein (1879-1955)
On Fri, 23 Oct 2020 at 16:24, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:
> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> w...@debian.org
>
> If you wish to submit further information on this problem, please
> send it to 933...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 933949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933949
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
diff --git a/lib/Test/FITesque.pm b/lib/Test/FITesque.pm
index 57f26df..9640a19 100644
--- a/lib/Test/FITesque.pm
+++ b/lib/Test/FITesque.pm
@@ -26,7 +26,7 @@ our $VERSION = '0.04';
L<Test::FITesque> is a framework designed to emulate the FIT L<http://fit.c2.com>
framework, but with a more perlish touch. While it is possible to use the FIT
-framework from within perl, it has a lot of unnessecary overhead related to its
+framework from within perl, it has a lot of unnecessary overhead related to its
origins in the Java world.
I created L<Test::FITesque> for the following reasons:
@@ -96,7 +96,7 @@ class. This first cell must refer to a method name in the Fixture class,
all following cells will be passed to the methods as arguments.
The run_tests() method on the FITesque test will simply run these methods
-in the order specified while taking care of maintaing TAP test count
+in the order specified while taking care of maintaining TAP test count
and the like underneath.
If you have more than one instance of a test to run, you can add it to a
@@ -220,7 +220,7 @@ L<Test::FITesque::Fixture>, L<Test::FITesque::Test>, L<Test::FITesque::Suite>
=head1 TEST COVERAGE
-This distribution is heavily unit and system tested for compatability with
+This distribution is heavily unit and system tested for compatibility with
L<Test::Builder>. If you come across any bugs, please send me or submit failing
tests to Test-FITesques RT queue. Please see the 'SUPPORT' section below on
how to supply these.
@@ -275,7 +275,7 @@ your bug as I make changes.
Due to limitations in the TAP protocol and perl's TAP tools such as
L<Test::Harness>, all Fixture tables have to be held in memory. It also means
that Fixture tables cannot be treated as a stream so there is no easy way
-to seperate out which tables output is which. To remedy this, I suggest that
+to separate out which tables output is which. To remedy this, I suggest that
you pass a 'name' parameter to the Fixture classes constructor and print this
to screen or use the diag() function from L<Test::More>.
