Re: Testing Zork-style game

K.I.S.S. Assuming that your using standard IO for your input and output, your test scripts could do something like:

use File::Slurp;
use Test::More ...;
...
system( 'perl zork.pl < testfile.1 >output.1' );
my $out = Slurp( 'output.1' );
my $expected = Slurp( 'expected.1' );

ok( $out eq $expected );
[download]

Substututing zork < testfile.1 > output.C.1 (C-version) or lisp zork.whatever? < testfile.1 >output.lisp.1 for the perl zork.pl in the system command allows you to run the same tests against all three versions.

Adding a debug option (to at least one version) that copies both the input and output to a separate files whilst the game is being played would allow you to generate your tests interactively with that version and then supply the input to the other versions and test their output was the same.

Examine what is said, not who speaks.

"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon

Comment on Re: Testing Zork-style game Select or Download Code

Replies are listed 'Best First'.
Re^2: Testing Zork-style game by petdance (Parson) on Jun 29, 2004 at 16:19 UTC
Except that you'd want to write `ok( $out eq $expected );` [download] as `is( $out, $expected );` [download] If the strings are really long and hard to read through, look at Test::LongString. xoxo, Andy	[reply] [d/l] [select]
Re^3: Testing Zork-style game by adrianh (Chancellor) on Jun 29, 2004 at 22:36 UTC
If the strings are really long and hard to read through, look at Test::LongString. Test::Differences can be useful for this too.	[reply]


Perl: the Markov chain saw
	PerlMonks