Ok, thanks for the explanation. I will comment this case out for now and
continue with the next sample program tomorrow. Once I have done the bulk of
the tests I will see how this can be integrated into the test workflow. Can
only do this on the side so it make take some time still.
And , if no
This is not going to work. You are using the rexx command to invoke the
program, which spins off a new process to run the program. Syntax errors
cannot be trapped across that boundary. If you invoke the program using the
CALL instruction, this will probably work. However, then you are unable to
use
Sorry, here the complete samples.testgroup
Samples.testGroup
Description: Binary data
Von meinen Macbook gesendetHälsningar/Regards/Grüsse,P.O. Jonssonoor...@jonases.se
Am 19.10.2018 um 21:51 schrieb Rick McGuire :Then show your failing test case method so we can see what
Here is the test case in question:
::method "test_011_interface.rex"
trace o
say
say '...running test method:' .context~name~lower
Line.1 = 'a Rectangle is a shape'
Line.2 = 'r~area: 10'
Line.3 = ''
Line.4 = 'a Circle is a shape'
Line.5 = 'c~area: 12.566370614359172954'
Line.6
Then show your failing test case method so we can see what you are doing
wrong. Just saying "it doesn't work" gives us no information about what
might be going wrong. For example, how are you invoking the program?
Rick
On Fri, Oct 19, 2018 at 3:42 PM P.O. Jonsson wrote:
> I was unclear: I am wr
I was unclear: I am writing test cases for ALL sample programs, the intention
is that they will go into the unit test framework later when I have done them
all. I promised Erich to have a go at it.
I have done 10 tests successfully so far, but for this one I could not get
around the error. I ha
This program is not using the unit test framework so expectSyntax is not
going to work.
Rick
On Fri, Oct 19, 2018 at 3:33 PM P.O. Jonsson wrote:
> Dear developers,
>
> In one of the sample files interface.rex there is an intended error
> produced to show the point. The output is the following: