use warnings; use strict; package Jifty::Test; use base qw/Test::More/; use Jifty::YAML; use Jifty::Server; use Jifty::Script::Schema; use Email::LocalDelivery; use Email::Folder; use File::Path; use File::Spec; use File::Temp; =head1 NAME Jifty::Test - Jifty's test module =head1 SYNOPSIS use Jifty::Test tests => 5; ...all of Test::More's functionality... ...any class methods defined below... =head1 DESCRIPTION Jifty::Test is a superset of Test::More. It provides all of Test::More's functionality in addition to the class methods defined below. =head1 METHODS =head2 is_passing my $is_passing = Jifty::Test->is_passing; Check if the test is currently in a passing state. * All tests run so far have passed * We have run at least one test * We have not run more than we planned (if we planned at all) =cut sub is_passing { my $tb = Jifty::Test->builder; my $is_failing = 0; $is_failing ||= grep {not $_} $tb->summary; $is_failing ||= $tb->has_plan eq 'no_plan' ? 0 : $tb->expected_tests < $tb->current_test; return !$is_failing; } =head2 is_done my $is_done = Jifty::Test->is_done; Check if we have run all the tests we've planned. If the plan is 'no_plan' then is_done() will return true if at least one test has run. =cut sub is_done { my $tb = Jifty::Test->builder; if( $tb->has_plan eq 'no_plan' ) { return $tb->current_test > 0; } else { return $tb->expected_tests == $tb->current_test; } } =begin private =head2 import_extra Called by L's C code when L is first C'd, it calls L, and asks Test::More to export its symbols to the namespace that C'd this one. =end private =cut sub import_extra { my $class = shift; $class->setup; Test::More->export_to_level(2); } =head2 setup Merges the L into the default configuration, resets the database, and resets the fake "outgoing mail" folder. This is the method to override if you wish to do custom setup work, such as insert test data into your database. =cut sub setup { my $class = shift; my $test_config = File::Temp->new( UNLINK => 0 ); Jifty::YAML::DumpFile($test_config, $class->test_config(Jifty::Config->new)); # Invoking bin/jifty and friends will now have the test config ready. $ENV{'JIFTY_TEST_CONFIG'} ||= $test_config; $class->builder->{test_config} = $test_config; { # Cache::Memcached stores things. And doesn't let them expire # from the cache easily. This is fine in production, but # during testing each test script needs its own namespace. we # use the pid of the current process, and save it so the keys # stays the same when we fork { package Jifty::Record; no warnings qw/redefine/; use vars qw/$cache_key_prefix/; $cache_key_prefix = "jifty-test-$$"; sub cache_key_prefix { $Jifty::Record::cache_key_prefix; } } } my $root = Jifty::Util->app_root; # Mason's disk caching sometimes causes false tests rmtree(["$root/var/mason"], 0, 1); Jifty->new( no_handle => 1 ); Log::Log4perl->get_logger("SchemaTool")->less_logging(3); my $schema = Jifty::Script::Schema->new; $schema->{drop_database} = $schema->{create_database} = $schema->{create_all_tables} = 1; $schema->run; Log::Log4perl->get_logger("SchemaTool")->more_logging(3); Jifty->new(); $class->setup_mailbox; } =head2 test_config Returns a hash which overrides parts of the application's configuration for testing. By default, this changes the database name by appending a 'test', as well as setting the port to a random port between 10000 and 15000. It is passed the current configuration. You can override this to provide application-specific test configuration, e.g: sub test_config { my $class = shift; my ($config) = @_; my $hash = $class->SUPER::test_config($config); $hash->{framework}{LogConfig} = "etc/log-test.conf" return $hash; } =cut sub test_config { my $class = shift; my ($config) = @_; return { framework => { Database => { Database => $config->framework('Database')->{Database} . "test", }, Web => { Port => int(rand(5000) + 10000), }, Mailer => 'Jifty::Test', MailerArgs => [], } }; } =head2 make_server Creates a new L which C L and returns it. =cut sub make_server { my $class = shift; # XXX: Jifty::TestServer is not a Jifty::Server, it is actually # server controller that invokes bin/jifty server. kill the # unshift here once we fix all the tests expecting it to be # jifty::server. if ($ENV{JIFTY_TESTSERVER_PROFILE} || $ENV{JIFTY_TESTSERVER_COVERAGE} || $ENV{JIFTY_TESTSERVER_DBIPROF} || $^O eq 'Win32') { require Jifty::TestServer; unshift @Jifty::Server::ISA, 'Jifty::TestServer'; } else { require Test::HTTP::Server::Simple; unshift @Jifty::Server::ISA, 'Test::HTTP::Server::Simple'; } Log::Log4perl->get_logger("Jifty::Server")->less_logging(3); my $server = Jifty::Server->new; return $server; } =head2 mailbox A mailbox used for testing mail sending. =cut sub mailbox { return Jifty::Util->absolute_path("t/mailbox"); } =head2 setup_mailbox Clears the mailbox. =cut sub setup_mailbox { my $class = shift; open my $f, ">:encoding(UTF-8)", $class->mailbox; close $f; } =head2 teardown_mailbox Deletes the mailbox. =cut sub teardown_mailbox { unlink mailbox(); } =head2 is_available Informs L that L is always available as a mailer. =cut sub is_available { 1 } =head2 send Should not be called manually, but is automatically called by L when using L as a mailer. (Note that it is a class method.) =cut sub send { my $class = shift; my $message = shift; Email::LocalDelivery->deliver($message->as_string, mailbox()); } =head2 messages Returns the messages in the test mailbox, as a list of L objects. You may have to use a module like L to parse multi-part messages stored in the mailbox. =cut sub messages { return Email::Folder->new(mailbox())->messages; } =head2 test_file my $files = Jifty::Test->test_file($file); Register $file as having been created by the test. It will be cleaned up at the end of the test run I the test passes. Otherwise it will be left alone. It returns $file so you can do this: my $file = Jifty::Test->test_file( Jifty::Util->absolute_path("t/foo") ); =cut my @Test_Files_To_Cleanup; sub test_file { my $class = shift; my $file = shift; push @Test_Files_To_Cleanup, $file; return $file; } =head2 test_in_isolation my $return = Jifty::Test->test_in_isolation( sub { ...your testing code... }); For testing testing modules so you can run testing code (which perhaps fail) without effecting the outer test. Saves the state of Jifty::Test's Test::Builder object and redirects all output to dev null before running your testing code. It then restores the Test::Builder object back to its original state. # Test that fail() returns 0 ok !Jifty::Test->test_in_isolation sub { return fail; }; =cut sub test_in_isolation { my $class = shift; my $code = shift; my $tb = Jifty::Test->builder; my $output = $tb->output; my $failure_output = $tb->failure_output; my $todo_output = $tb->todo_output; my $current_test = $tb->current_test; $tb->output( File::Spec->devnull ); $tb->failure_output( File::Spec->devnull ); $tb->todo_output( File::Spec->devnull ); my $result = $code->(); $tb->output($output); $tb->failure_output($failure_output); $tb->todo_output($todo_output); $tb->current_test($current_test); return $result; } # Stick the END block in a method so we can test it. END { Jifty::Test->_ending } sub _ending { my $Test = Jifty::Test->builder; # Such a hack -- try to detect if this is a forked copy and don't # do cleanup in that case. return if $Test->{Original_Pid} != $$; # If all tests passed.. if (Jifty::Test->is_passing && Jifty::Test->is_done) { # Clean up mailbox Jifty::Test->teardown_mailbox; # Remove testing db if (Jifty->handle) { Jifty->handle->disconnect(); Log::Log4perl->get_logger("SchemaTool")->less_logging(3); my $schema = Jifty::Script::Schema->new; $schema->{drop_database} = 1; $schema->run; Log::Log4perl->get_logger("SchemaTool")->more_logging(3); } # Unlink test files unlink @Test_Files_To_Cleanup; } # Unlink test file unlink $Test->{test_config} if $Test->{test_config}; } 1;