Just an FYI regarding the test suite.
One of my original ideas for the test suite was to make it easy to run
a different set of tests by using a different file extension for the
set of test files. But, I had never finished the implementation. I
recently completed the implementation.
The "-e" option of testOORexx.rex will cause the test to collect a
different set of test group files using the specified extension. A
different extension than .testGroup which is the default extension.
As an example, I added some test group files for ooDialog, that work
well on Windows. The file extension is .oodTestGroup, and you can
executed all the ooDialog tests by using this command line:
testOORexx.rex -e oodTestGroup
The reason I added the oodTestGroup extension is that I was having
trouble getting the ooDialog.cls package loaded with everything in the
proper scope. As I'm sure you all recall, if you put a "::requires
'ooDialog.cls'" statement directly in the the test group file, an
error is generated when the test suite is run on a non-Windows OS.
When I used:
.context~package~loadPackage('ooDialog.cls')
to indirectly load the package, after the prologue had already
executed, my test dialog subclass in the file could not be
constructed. Using an alternate extension allows things to work
cleanly. It also allows someone interested in just the ooDialog tests
to easily just work with that subset of the tests.
--
Mark Miesfeld
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
