perlquestion McMahon In [id://370258|this node], [dragonchild] explains how he's going to build a text-based adventure game in several languages, and wonders how to test his code. <br><br> [pbeckingham] recommends [id://370260|testing at the user interface] with [cpan://Expect].<br><br> [adrianh] recommends [id://370274|writing a common api] for each implementation and script the testing through the API.<br><br> [andyf] adds a recommendation to [id://370281|write a state-dumping function].<br><br> [sgifford] recommends [id://370315|controlling the testing with a 2-way pipe] in and out of the game. <br><br> [BrowserUK] suggests [id://370407|a simple but multidisciplinary approach] with a simple script recorder controlled through [cpan://Test::More].<br><br> That is already a lot of interfaces to test a simple command-line program, and we didn't even hear from the Haskell program-by-contract camp (who talk about testable interfaces a lot) or the FIT alternate-UI camp (who are trying to figure out how to do agile user testing). <br><br> So:<br> Is there a best way to build an interface for testing?<br> Are there contexts in which one test interface is better than another?