Re: [Oorexx-devel] Running Testcases

Also when I make the macrospaces testgroup work there are plenty of failing tests, I have enclosed a complete result (copied from the terminal session as-is)Is this a meaningful feedback form? or should I try to pinpoint each individual problem (to the best of my abilities) and send them as „bugs“?

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] Running Testcases

dear Bruce, I have updated using svn to todays built r11519, created an installer and installed a working installation of ooRexx. I have also downloaded the corresponding test folder structure: oorexx-code-0-r11519-test-trunk/ Then I move into oorexx-code-0-r11519-test-trunk/ and set up the

Re: [Oorexx-devel] Running Testcases

That depends. you need to pull ooTest from the same build level, I believe. Bruce > On Nov 18, 2018, at 11:50 AM, P. O. Jonsson wrote: > > Thanks for the info, I have done it the way you proposed including the shell > script but I have an older build of ooRexx, can that be the problem? > > I w

Re: [Oorexx-devel] Running Testcases

Thanks for the info, I have done it the way you proposed including the shell script but I have an older build of ooRexx, can that be the problem? I will try further tomorrow, thanks for all the feedback. Hälsningar/Regards/Grüsse, P. O. Jonsson Von meinem iPhone gesendet > Am 18.11.2018 um 20:

Re: [Oorexx-devel] Running Testcases

I looked at some of my runs from many years ago, and the run time was less then three minutes. Also, after a test run be sure that all of the files created during the test run are deleted. They should be, but double check. Also my prior comment (off line) regarding RXAPI. It is probably best

Re: [Oorexx-devel] Running Testcases

It’s been a while since I’ve run the test suite, but it shouldn’t take more than 15 minutes or so. In the past, I’ve run into the situation that you have, and it generally means that either your invocation or your environment isn’t set up correctly. Bruce > On Nov 18, 2018, at 10:41 AM, P.O. Jo

[Oorexx-devel] Running Testcases

Dear Developers, I have downloaded the test environment from : https://svn.code.sf.net/p/oorexx/code-0/test/trunk as suggested by Rick and have started to run the available test cases (on a Mac). It has now been running for four hours and I