To follow up on this thread with a couple of other tips, for people interested.
To run the test suite but skip all the API tests, maybe because you
don't have the libraries built:
E:\work.ooRexx\3.x\main\Win32Dbg>.\rexx
\work.ooRexx\ooRexxUnit\4.0\testOORexx.rex -R ooRexx\API -X native_api
Searching for test containers..
Executing automated test suite..
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter: REXX-ooRexx_4.0.0(MT) 6.03 9 Sep 2008
ooRexxUnit: 2.0.0_3.2.0 ooTest: 1.0.0_3.2.0
Tests ran: 1
Assertions: 0
Failures: 0
Errors: 0
Skipped files: 2
File search: 00:00:00.016000
Suite construction: 00:00:00.000000
Test execution: 00:00:00.000000
Total time: 00:00:01.000000
E:\work.ooRexx\3.x\main\Win32Dbg>
The above shows that 2 test groups were skipped. To get more info on
skipped test groups, you up the verbosity:
E:\work.ooRexx\3.x\main\Win32Dbg>.\rexx
\work.ooRexx\ooRexxUnit\4.0\testOORexx.rex -R ooRexx\API -X native_api
-V 5
Searching for test containers..
Executing automated test suite..
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter: REXX-ooRexx_4.0.0(MT) 6.03 9 Sep 2008
ooRexxUnit: 2.0.0_3.2.0 ooTest: 1.0.0_3.2.0
Tests ran: 1
Assertions: 0
Failures: 0
(Known failures:) 0
Errors: 0
Exceptions: 0
Skipped files: 2
Messages: 0
[Skipped test group] [20080910 16:46:22.114000]
File: E:\work.ooRexx\ooRexxUnit\4.0\ooRexx\API\oo\FUNCTION.testGroup
The test container has no executable tests
This is a native API test and not included in the test types to execute.
[Skipped test group] [20080910 16:46:22.130000]
File: E:\work.ooRexx\ooRexxUnit\4.0\ooRexx\API\oo\METHOD.testGroup
The test container has no executable tests
This is a native API test and not included in the test types to execute.
Interpreter: REXX-ooRexx_4.0.0(MT) 6.03 9 Sep 2008
ooRexxUnit: 2.0.0_3.2.0 ooTest: 1.0.0_3.2.0
Tests ran: 1
Assertions: 0
Failures: 0
(Known failures:) 0
Errors: 0
Exceptions: 0
Skipped files: 2
Messages: 0
File search: 00:00:00.031000
Suite construction: 00:00:00.000000
Test execution: 00:00:00.000000
Total time: 00:00:01.000000
E:\work.ooRexx\3.x\main\Win32Dbg>
Then, let's say you didn't skip the API tests, but you don't have the
libraries built. You will get output like this:
E:\work.ooRexx\3.x\main\Win32Dbg>.\rexx
\work.ooRexx\ooRexxUnit\4.0\testOORexx.rex -R ooRexx\API -V 5
Searching for test containers..
Executing automated test suite..
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter: REXX-ooRexx_4.0.0(MT) 6.03 9 Sep 2008
ooRexxUnit: 2.0.0_3.2.0 ooTest: 1.0.0_3.2.0
Tests ran: 1
Assertions: 0
Failures: 0
(Known failures:) 0
Errors: 0
Exceptions: 2
Skipped files: 0
Messages: 0
[Framework exception] [20080910 16:48:10.605000]
File: E:\work.ooRexx\ooRexxUnit\4.0\ooRexx\API\oo\FUNCTION.testGroup
Line: 69
Type: Trap Severity: Fatal
Unable to load library "orxfunction"
69 *-* .context~package~loadPackage('FUNCTIONPackage.cls')
[Framework exception] [20080910 16:48:10.621000]
File: E:\work.ooRexx\ooRexxUnit\4.0\ooRexx\API\oo\METHOD.testGroup
Line: 69
Type: Trap Severity: Fatal
Unable to load library "orxmethod"
69 *-* .context~package~loadPackage('METHODPackage.cls')
Interpreter: REXX-ooRexx_4.0.0(MT) 6.03 9 Sep 2008
ooRexxUnit: 2.0.0_3.2.0 ooTest: 1.0.0_3.2.0
Tests ran: 1
Assertions: 0
Failures: 0
(Known failures:) 0
Errors: 0
Exceptions: 2
Skipped files: 0
Messages: 0
File search: 00:00:00.031000
Suite construction: 00:00:00.000000
Test execution: 00:00:00.000000
Total time: 00:00:01.000000
E:\work.ooRexx\3.x\main\Win32Dbg>
--
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
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
