Hi Mark,
I downloaded the most recent version of the test and ran it with only one
(1) failure this time around.
NOTE: I am still running the test suite in the "C:\Program Files\"
directory path. To be specific, the base directory is: "C:\Program
Files\ooRexx\ooTest-4.2.0-snapshot06A"
NOTE: I tried using the -l flag but never saw the file name I specify show
up. I did find a ooTest.log file, though (see below). The command I
tried with the -l was:
testOORexx -X native_api -l ooTest_2014_02_16_03_05.log
did I do it incorrectly? What I was expecting to find was a file with the
spec of: ooTest_2014_02_16_03_05.log most likely in the "C:\Program
Files\ooRexx\ooTest-4.2.0-snapshot06A" directory.
Anyway, the test suit run and I did find a log file (see below) with the
failure.
>From what I can tell, when using the Command Prompts with admin rights /
privileges enabled, the temporary files exist. At least I'm seeing files
with a date and time created during the run, such as: tempRxPrgFile.rex
SCICAL4A TestRxQueue.rex ooTest.log
The ooTest.log file (found in the directory: C:\Program
Files\ooRexx\ooTest-4.2.0-snapshot06A\ooRexx\base\rexxutil\platform\windows)
contains:
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter: REXX-ooRexx_4.2.0(MT)_64-bit 6.04 30 Jan 2014
Addressing Mode: 64
ooRexxUnit: 2.0.0_3.2.0 ooTest: 1.0.0_4.0.0
Tests ran: 19635
Assertions: 577422
Failures: 1
Errors: 0
Skipped files: 12
[failure] [20140216 03:07:25.070000]
svn: r3371 Change date: 2008-09-20 21:33:29 -0700
Test: TEST_4
Class: CALL.testGroup
File: C:\Program Files\...\ooRexx\base\keyword\CALL.testGroup
Line: 245
Failed: assertTrue
Expected: [1]
Actual: [[0], identityHash="1099511324900"]
Message: subTest4-gt id: 1004 TIME('E')>1
File search: 00:00:05.617000
Suite construction: 00:00:01.376000
Test execution: 00:04:00.336000
Total time: 00:04:08.341000
Using the -f flage (no -l this time), I got:
Sun 02/16/2014 3:23:44.16 C:\Program
Files\ooRexx\ooTest-4.2.0-snapshot06A>testOORexx -X native_api -f
ooRexx\base\keyword\CALL.tes
tGroup
Searching for test containers..
Executing automated test suite...
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter: REXX-ooRexx_4.2.0(MT)_64-bit 6.04 30 Jan 2014
Addressing Mode: 64
ooRexxUnit: 2.0.0_3.2.0 ooTest: 1.0.0_4.0.0
Tests ran: 16
Assertions: 131
Failures: 0
Errors: 0
Skipped files: 0
File search: 00:00:00.010000
Suite construction: 00:00:00.001000
Test execution: 00:00:01.101000
Total time: 00:00:02.017000
NOTE: The ooTest.log file did NOT change. It still looks the same as it
after the first run (see above).
I'm going to try running the entire suite again this time with the "-s"
option. I won't append it here, but in another email to come (assuming
there is something interesting). I'm doing this to keep the size of
messages down.
I hope this testing is helping.
Bert.
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
