Re: [Oorexx-devel] Test Case Structure Questions

[Gil B. <gi...@be...>]

Thanks, Mark.  I'll check it out when I have some time to study it.

Mark Miesfeld wrote:
> Gil,
> 
> Take a look at ooRexx/samples/ooDialog/examples/fileNameDialog_demo.testGroup
> 
> I tried to put a lot of comment in that.  It shows how to have the
> test methods execute in the order you want.  And, I also use a flag
> that signals a test should not continue.
> 
> --
> Mark Miesfeld
> 
> On Jan 17, 2008 12:21 PM, Gil Barmwater <gi...@be...> wrote:
> 
>>Lee has been showing me the testcases he has been developing and
>>"suggesting" that I work on the RxSock functions testcases.  Well, I got
>>a copy of the documentation to refresh my memory on what all is in there
>>and I came up with some questions (besides "where do I start?" and "what
>>have I gotten myself into?").
>>
>>All of the tescases I have seen are what I will call "standalone".  That
>>is, other than some simple preliminary code, the test asserts that some
>>function returns an expected value (or creates an expected error).  For
>>the RxSock functions, there is some "state" requirements or required
>>order of execution.  One cannot do a SockSend if one hasn't already
>>successfully done a SockConnect for example.
>>
>>Now, one could construct a testcase that does functionA followed by
>>functionB and then "test" that functionC works correctly but I can see
>>(in this case) three failures if functionA doesn't work: the testcase
>>for functionA, and also the ones for functionB and for functionC.  This
>>only gets worse as we get deeper into the sequence of function calls.
>>
>>A possible way around this is to set a "global" variable to indicate
>>that an error has occurred and have each test check it before attempting
>>to execute.  So the first testcase would just test functionA.  The
>>second testcase would only run functionB if tescase 1 was successful.
>>
>>So, finally, the question is do we have examples of this type of
>>structure already or am I the first to run into it?  And if I am (lucky
>>me!), what do you suggest as a way to structure these types of tests?
>>--
>>Gil Barmwater
>>
>>
>>-------------------------------------------------------------------------
>>This SF.net email is sponsored by: Microsoft
>>Defy all challenges. Microsoft(R) Visual Studio 2008.
>>http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>_______________________________________________
>>Oorexx-devel mailing list
>>Oor...@li...
>>https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Oorexx-devel mailing list
> Oor...@li...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> 
> 

-- 
Gil Barmwater