Re: [Oorexx-devel] Running Testcases

Darwin Kernel Version 17.7.0: Wed Oct 10 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64.17.7.0 Tests ran: 37 Assertions: 32 Failures: 11 Errors: 0 [failure] [20181119 20:46:51.751475] svn:r11306 Change date: 2017-10-07 18:21:20 + Test

Re: [Oorexx-devel] Running Testcases

Dear Bruce, this is what I have done so far as well. I am leaning heavily against the readme.first At least I am underway now. Von meinen Macbook gesendet Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 19.11.2018 um 20:36 schrieb CV Bruce : > > I also see in my notes (emails

Re: [Oorexx-devel] Running Testcases

I have pinpointed the first problem. in the macrospace.testgroup, this assertion is the culprit, when I comment it out the test case executes to the end, all other assertions are ok. ::method test_clear -- add a macro, query it, clear macrospace, and query again self~assertEquals(self~OK, S

Re: [Oorexx-devel] Running Testcases

I also see in my notes (emails) that some tests will fail if your try to redirect the output of ooTest to a file. If I remember correctly, I would just let all the output go to the screen, and then cut and paste the screen buffer into a text document. Bruce > On Nov 19, 2018, at 11:24 AM, P.O.

Re: [Oorexx-devel] Running Testcases

"Boing-Boing" means that the machine produces a noise „boing!“ five times in a row at exactly the time I see a space instead of a dot in the execution output. I cannot describe it better than that, it must be an error raised. I will try to pinpoint each error. Von meinen Macbook gesendet Hälsn

Re: [Oorexx-devel] Running Testcases

Dear Eric, thanks for responding, answer below inline. Von meinen Macbook gesendetHälsningar/Regards/Grüsse,P.O. Jonssonoor...@jonases.se Am 19.11.2018 um 19:09 schrieb Erich Steinböck :Hi P.O.,good practice is to run tests with `testOORexx -s -X native_API`If in additi

Re: [Oorexx-devel] Running Testcases

> > a potential problem (I think) is the need to use ./ to refer to the > testcases on Mac (deprecated) > Can you please explain? Which unexpected behaviour are you seeing? On Mon, Nov 19, 2018 at 7:09 PM Erich Steinböck wrote: > Hi P.O., > good practice is to run tests with `testOORexx -s -X

Re: [Oorexx-devel] Running Testcases

Hi P.O., good practice is to run tests with `testOORexx -s -X native_API` If in addition if you suppress long-running tests with e. g. `-x CHAROUT TIME Alarm Message ticker WindowsEventLog` tests will finish in a minute or less. When something goes wrong, the last test group printed should be the

Re: [Oorexx-devel] Running Testcases

Bruce, On 19.11.2018 16:14, CV Bruce wrote: > Does anyone know if there is a “verbose” option that would print out test > results as each test is > performed? That way we can at least see where we are dying. you can see the most important switches with: testOORexx --help So the switch "-S"

Re: [Oorexx-devel] Running Testcases

Does anyone know if there is a “verbose” option that would print out test results as each test is performed? That way we can at least see where we are dying. Bruce > On Nov 18, 2018, at 3:45 PM, P.O. Jonsson wrote: > > dear Bruce, > > I have updated using svn to todays built r11519, created a

Re: [Oorexx-devel] Building test cases

Hi Leslie > > 1) Those of us who do not type 'rexx [execname]' would not like to > have to > learn to do that. :-) No, I can see that. Note that in Linux, Mac, and other Unix derivatives, you need to specify the full suffix on the filename, while on OS/2, VM and a well adapted Wi

Re: [Oorexx-devel] Advice needed on redirecting/picking up output

thanks, I will look at that. I am only doing some elementary tests, the use pipe does more. I only wanted to have at least a few tests for each item. Von meinen Macbook gesendet Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 19.11.2018 um 11:56 schrieb Rick McGuire : > > the

Re: [Oorexx-devel] Advice needed on redirecting/picking up output

the ADDRESS.TestGroup contains an ArrayOutputStream class that you use with .output~destination to capture the output. However, unless you are specifically testing the displayer stage (one or two tests at most), you are better off writing these tests using the arraycollector stage as the end stage

[Oorexx-devel] Advice needed on redirecting/picking up output

Dear Developers, I am writing a rudimentary test case for pipe.cls. There is a usepipe.rex that requires this class and make some tests and I have looked at them and tried to do some complementary tests but I get stuck in that I can not get hold of the output that goes to standard output (the t