# You may distribute under the terms of either the GNU General Public License # or the Artistic License (the same terms as Perl itself) # # (C) Paul Evans, 2007-2012 -- leonerd@leonerd.org.uk package IO::Async::Test; use strict; use warnings; our $VERSION = '0.55'; use Exporter 'import'; our @EXPORT = qw( testing_loop wait_for wait_for_stream ); =head1 NAME C - utility functions for use in test scripts =head1 SYNOPSIS use Test::More tests => 1; use IO::Async::Test; use IO::Async::Loop; my $loop = IO::Async::Loop->new; testing_loop( $loop ); my $result; $loop->do_something( some => args, on_done => sub { $result = the_outcome; } ); wait_for { defined $result }; is( $result, what_we_expected, 'The event happened' ); ... my $buffer = ""; my $handle = IO::Handle-> ... wait_for_stream { length $buffer >= 10 } $handle => $buffer; is( substr( $buffer, 0, 10, "" ), "0123456789", 'Buffer was correct' ); =head1 DESCRIPTION This module provides utility functions that may be useful when writing test scripts for code which uses C (as well as being used in the C test scripts themselves). Test scripts are often synchronous by nature; they are a linear sequence of actions to perform, interspersed with assertions which check for given conditions. This goes against the very nature of C which, being an asynchronisation framework, does not provide a linear stepped way of working. In order to write a test, the C function provides a way of synchronising the code, so that a given condition is known to hold, which would typically signify that some event has occured, the outcome of which can now be tested using the usual testing primitives. Because the primary purpose of C is to provide IO operations on filehandles, a great many tests will likely be based around connected pipes or socket handles. The C function provides a convenient way to wait for some content to be written through such a connected stream. =cut my $loop; =head1 FUNCTIONS =cut =head2 testing_loop( $loop ) Set the C object which the C function will loop on. =cut sub testing_loop { $loop = shift; } =head2 wait_for( $condfunc ) Repeatedly call the C method on the underlying loop (given to the C function), until the given condition function callback returns true. To guard against stalled scripts, if the loop indicates a timeout for 10 consequentive seconds, then an error is thrown. =cut sub wait_for(&) { my ( $cond ) = @_; my ( undef, $callerfile, $callerline ) = caller; my $timedout = 0; my $timerid = $loop->watch_time( after => 10, code => sub { $timedout = 1 }, ); $loop->loop_once( 1 ) while !$cond->() and !$timedout; if( $timedout ) { die "Nothing was ready after 10 second wait; called at $callerfile line $callerline\n"; } else { $loop->unwatch_time( $timerid ); } } =head2 wait_for_stream( $condfunc, $handle, $buffer ) As C, but will also watch the given IO handle for readability, and whenever it is readable will read bytes in from it into the given buffer. The buffer is NOT initialised when the function is entered, in case data remains from a previous call. C<$buffer> can also be a CODE reference, in which case it will be invoked being passed data read from the handle, whenever it is readable. =cut sub wait_for_stream(&$$) { my ( $cond, $handle, undef ) = @_; my $on_read; if( ref $_[2] eq "CODE" ) { $on_read = $_[2]; } else { my $varref = \$_[2]; $on_read = sub { $$varref .= $_[0] }; } $loop->watch_io( handle => $handle, on_read_ready => sub { my $ret = $handle->sysread( my $buffer, 8192 ); if( !defined $ret ) { die "Read failed on $handle - $!\n"; } elsif( $ret == 0 ) { die "Read returned EOF on $handle\n"; } $on_read->( $buffer ); } ); # Have to defeat the prototype... grr I hate these &wait_for( $cond ); $loop->unwatch_io( handle => $handle, on_read_ready => 1, ); } =head1 AUTHOR Paul Evans =cut 0x55AA;