unit test is not always the correct term

mojolicious · Mar 9, 2014 · 66a5661 · 66a5661
1 parent ad0233b
commit 66a5661
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 9 deletions.
diff --git a/lib/Mojolicious/Command/test.pm b/lib/Mojolicious/Command/test.pm
@@ -7,7 +7,7 @@ use File::Spec::Functions qw(abs2rel catdir splitdir);
 use Getopt::Long qw(GetOptionsFromArray :config no_auto_abbrev no_ignore_case);
 use Mojo::Home;
 
-has description => 'Run unit tests.';
+has description => 'Run tests.';
 has usage => sub { shift->extract_usage };
 
 sub run {

diff --git a/lib/Mojolicious/Guides/Cookbook.pod b/lib/Mojolicious/Guides/Cookbook.pod
@@ -787,8 +787,8 @@ right in.
 Scraping information from web sites has never been this much fun before. The
 built-in HTML/XML parser L<Mojo::DOM> is accessible through
 L<Mojo::Message/"dom"> and supports all CSS selectors that make sense for a
-standalone parser, it can be a very powerful tool especially for unit testing
-web application.
+standalone parser, it can be a very powerful tool especially for testing web
+application.
 
   use Mojo::UserAgent;
 

diff --git a/lib/Mojolicious/Guides/Growing.pod b/lib/Mojolicious/Guides/Growing.pod
@@ -384,8 +384,8 @@ depending on browser.
 
 =head2 Final prototype
 
-A final C<myapp.pl> prototype passing all of the unit tests above could look
-like this.
+A final C<myapp.pl> prototype passing all of the tests above could look like
+this.
 
   #!/usr/bin/env perl
   use Mojolicious::Lite;
@@ -558,7 +558,7 @@ applications can use nested routes they have no need for C<group> blocks.
 =head2 Simplified application script
 
 C<myapp.pl> itself can now be turned into a simplified application script to
-allow running unit tests again.
+allow running tests again.
 
   #!/usr/bin/env perl
 

diff --git a/lib/Mojolicious/Lite.pm b/lib/Mojolicious/Lite.pm
@@ -970,8 +970,7 @@ specific C<exception> and C<not_found> templates.
 =head2 Testing
 
 Testing your application is as easy as creating a C<t> directory and filling
-it with normal Perl unit tests, which can be a lot of fun thanks to
-L<Test::Mojo>.
+it with normal Perl tests, which can be a lot of fun thanks to L<Test::Mojo>.
 
   use Test::More;
   use Test::Mojo;
@@ -984,7 +983,7 @@ L<Test::Mojo>.
 
   done_testing();
 
-Run all unit tests with the command L<Mojolicious::Command::test>.
+Run all tests with the command L<Mojolicious::Command::test>.
 
   $ ./myapp.pl test
   $ ./myapp.pl test -v