Hi all,

The solution I've taken is in my comment further down.

I have a module that contains an interactive script. For this script I would like to write a regression test for the behaviour on EOF of the input (it should exit cleanly with a defined output).

My first idea was, to use IPC::Open2 as written in perlipc. But then I would have to implement some timer to make sure the script exits at all.

My next idea was, to try something with Expect. But I can't see a way to close stdin for the process within Expect.

So that's where I am, any hints/suggestions appreciated.

Mathias

Update. To make it more clear here is some code.

Given this script

while(1) {
    if (eof(STDIN)) {
        print "END";
        exit;
    }
    $_ = <STDIN>;
    if (/^q/i) {
        print "END";
        exit;
    }
    print;
    print '$ ';
}
[download]

and this test

#!/usr/bin/perl -w
#
use Test::More tests => 4;

use Expect;
$script = './test1-script.pl';
@match_pattern = ( [ qr/END/ => sub { print "\n"; ok(1,"got end"); } ]
+ );
#----------------------- 1 ---------------------------
$exp = Expect->spawn($script);
$exp->send("q\n");
$exp->expect(10, @match_pattern);
#----------------------- 2 ---------------------------
$exp = Expect->spawn($script);
$exp->send("\4\n");
$exp->expect(10, @match_pattern);
#=====================================================
use IPC::Open3;
#----------------------- 3 ---------------------------
$pid = open3($in, $out, $err, $script);
print $in "q\n";
like(<$out>,qr/END/,"Quit");
waitpid($pid, 0);
#----------------------- 4 ---------------------------
$pid = open3($in, $out, $err, $script);
close $in;
like(<$out>,qr/END/,"EOF in Input");
waitpid($pid, 0);
[download]

I get mostly what I want.

I see the following problems:

• The $exp->send("\4\n"); in 2 is not portable. It depends on the operating system and the settings of the tty AFAIK
• 3 and 4 lack the timeout, so the test hangs if the tested script fails to exit.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.