Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

typos in documentation #318

Merged
merged 1 commit into from Jun 7, 2012
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion lib/TB2/CanLoad.pm
Expand Up @@ -10,7 +10,7 @@ $VERSION = eval $VERSION; ## no critic (BuiltinFunctions::ProhibitStringyEval

=head1 NAME

TB2::CanLoad - load modules without effecting global variables
TB2::CanLoad - load modules without affecting global variables

=head1 SYNOPSIS

Expand Down
4 changes: 2 additions & 2 deletions lib/Test/Builder.pm
Expand Up @@ -56,7 +56,7 @@ work together>.
Returns a Test::Builder object representing the current state of the
test.

Since you only run one test per program C<new()> always returns the same
Since you only run one test per program, C<new()> always returns the same
Test::Builder object. No matter how many times you call C<new()>, you're
getting the same object. This is called the default. This is done so that
multiple modules share such global information as the test counter and
Expand Down Expand Up @@ -1173,7 +1173,7 @@ These methods are useful when writing your own test methods.
$Test->maybe_regex('/$regex/');

This method used to be useful back when Test::Builder worked on Perls
before 5.6 which didn't have qr//. Now its pretty useless.
before 5.6 which didn't have qr//. Now it's pretty useless.

Convenience method for building testing functions that take regular
expressions as arguments.
Expand Down
18 changes: 9 additions & 9 deletions lib/Test/More.pm
Expand Up @@ -692,7 +692,7 @@ sub new_ok {

C<subtest()> runs the C<&code> as its own little test with its own plan and
its own result. The main test counts this as a single test using the
result of the whole subtest to determine if its ok or not ok.
result of the whole subtest to determine if it's ok or not ok.

For example...

Expand Down Expand Up @@ -1003,11 +1003,11 @@ B<NOTE> I'm not quite sure what will happen with filehandles.
is_deeply( $got, $expected, $test_name );

Similar to C<is()>, except that if C<$got> and C<$expected> are references, it
does a deep comparison walking each data structure to see if they are
does a deep comparison, walking each data structure to see if they are
equivalent. If the two structures are different, it will display the
place where they start differing.

C<is_deeply()> compares the dereferenced values of references, the
C<is_deeply()> compares the dereferenced values of references. The
references themselves (except for their type) are ignored. This means
aspects such as blessing and ties are not considered "different".

Expand Down Expand Up @@ -1163,7 +1163,7 @@ You might remember C<ok() or diag()> with the mnemonic C<open() or
die()>.

B<NOTE> The exact formatting of the diagnostic output is still
changing, but it is guaranteed that whatever you throw at it it won't
changing, but it is guaranteed that whatever you throw at it, it won't
interfere with the test.

=item B<note>
Expand Down Expand Up @@ -1400,9 +1400,9 @@ but want to put tests in your testing script (always a good idea).
Indicates to the harness that things are going so badly all testing
should terminate. This includes the running of any additional test scripts.

This is typically used when testing cannot continue such as a critical
This is typically used when testing cannot continue, such as a critical
module failing to compile or a necessary external utility not being
available such as a database connection failing.
available, such as a database connection failing.

The test will exit with 255.

Expand Down Expand Up @@ -1827,7 +1827,7 @@ L<Test::Harness> is the test runner and output interpreter for Perl.
It's the thing that powers C<make test> and where the C<prove> utility
comes from.

L<Test::Legacy> tests written with Test.pm, the original testing
L<Test::Legacy>. Tests written with Test.pm, the original testing
module, do not play well with other testing libraries. Test::Legacy
emulates the Test.pm interface and does play well with others.

Expand All @@ -1845,8 +1845,8 @@ L<Bundle::Test> installs a whole bunch of useful test modules.

=head1 AUTHORS

Michael G Schwern E<lt>schwern@pobox.comE<gt> with much inspiration
from Joshua Pritikin's Test module and lots of help from Barrie
Michael G Schwern E<lt>schwern@pobox.comE<gt>, with much inspiration
from Joshua Pritikin's Test module, and lots of help from Barrie
Slaymaker, Tony Bowden, blackstar.co.uk, chromatic, Fergal Daly and
the perl-qa gang.

Expand Down