I've been trying to write some tests for the RexxInstance APIs and the new style exit handlers. For the most part, having an external function or method that gets called by the main test code is not going to work. A lot of these tests really need to be run in a separate process. Right now, my approach will be to have a single large .exe file that implements multiple test variations that are invoked with command line arguments. Generally, the arguments would be something like this:
runTests testid options program arguments .... where the test id will determine the setup that needs to be performed to run a particular test, the options will give fine-tuned control of the setup (for example, enabling or disabling particular exits), the program name will be the name of a program that will be run for a given tests. The executed program will be passed any additional arguments when it's invoked. I think this will do everything I need it to do in terms of testing the functions, but I'm not really sure how to handle the reporting. Right now, my best thinking is to use a defined queue for passing back assertion results. So for these tests, there will be a second framework class that maybe just has class methods to handle assertions. Assertion failure would just push a line on to the queue in some sort of format that can be processed once the runTests command completes. I think this will work, but I've got a couple of concerns: 1) It would be nice to be able to log successes as well as failures, so the code that processes the queue should be able to update statistics accordingly. 2) A given test run might give multiple assertion failures. It would be nice if the infrastructure could "drain the stack", log the failures, then only raise the assertion failure error once everything has been handled. Can anybody think of other approaches we might use? Rick ------------------------------------------------------------------------- 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
