On Thu, Oct 9, 2008 at 7:21 AM, Mark Miesfeld <[EMAIL PROTECTED]> wrote: > On Thu, Oct 9, 2008 at 6:47 AM, Rick McGuire <[EMAIL PROTECTED]> wrote:
> You would have your external binary that implemented whatever APIs you > are testing. > > From within the existing framework you execute the binary in a > separate process passing whatever arguments you want to test different > things. The framework captures both the return code from the external > binary and also any console output. Within the existing framework you > assert that the return code is what you want. You can also assert > that the console output is what you expect. If the external binary was one that didn't have a console, so that it couldn't generate normal console output, we could use your idea of a defined queue to send results back to the test framework. Add a new public function, something like executePrgWithQueue(cmd, nameOfQueue) In the test method you would create the named queue, pass the name to the execute function. Then on return pull the lines from the queue and assert that each line is as expected. (Started writing this before your update.) -- Mark Miesfeld ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
