API testing is moving along pretty good for the APIs where the tests can/need to be driven from ooRexx code. There are a lot of tests, however, that test creation of interpreter instances and the various upfront bits such as enabling exits, etc. I can see two basic approaches to this: 1) create a bunch of small executable files (.exe) files, one for each test variation, or 2) create a single large file that contains all of the variations, with individual tests being invoked by a command line option. There will likely be a lot of infrastructure code shared between the tests, which might make option 2) more attractive. Option 1 might result in simpler executables that are easier to manage, but we'd need to have a setup for sharing common code between the tests.
I'm sitting on the fence on this one, so I think I'll defer the decision to Mark and David, who have been the ones largely responsible for putting together the API test framework and build. 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 Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
