[Cuis] Canonical test cases?

Phil (list) pbpublist at gmail.com
Sun Jul 19 19:43:29 CDT 2015


Hi Hannes,

On Sun, 2015-07-19 at 23:52 +0000, H. Hirzel wrote:
> On 2/23/15, Phil (list) <pbpublist at gmail.com> wrote:
> > On Mon, 2015-02-23 at 07:53 -0800, Ken.Dickey wrote:
> >> On Mon, 23 Feb 2015 08:38:44 +0000
> >> "H. Hirzel" <hannes.hirzel at gmail.com> wrote:
> >>
> >> > As Casey writes "The hard part is time and energy to do so."
> >> >
> >> > So what can be done with minimal effort and big impact?
> >>
> >> Looking around, I see that I could make some simple naming changes for
> >> test cases.
> >>
> >> E.g in package Crypto-Nacl there are test cases (class NaclTests)
> >>   testExampleHighlevel -> testNaclHiglLevelAPI
> >>   textExampleLowLevel -> testNaclLowLevelAPI
> >>
> >> We could use other words, but API is shorter than Usage, Example,
> >> Interface.
> >>
> >> Having specific test names end in 'API' would clue me in.
> >>
> >> Adding 'Nacl' means I can use the existing message finder to search for
> >> 'api' and note testNacl*API methods.  This lets me find API tests specific
> >> to Nacl.
> >>
> >> And we can do this as I get the chance.
> >>
> >> Other suggestions?
> >
> > I started playing around with a couple of example test cases to see what
> > I ran into and came up with a distinct class to store all of these per
> > test category (i.e. under Test-Files a class ApiFile which could have a
> > method testWriteTextFile)  The rationale was that it might make sense to
> > keep these test cases separate from traditional test cases which are
> > free to make calls that users of the class (i.e. who are calling the
> > supported API) should not.
> 
> Phil,
> 
> where do you keep this class ApiFile?
> 

It's in Packages/Tests.pck.st package. After loading it will be listed
in the Tests-Files category.

> regards
> 
> Hannes
> 

Thanks,
Phil





More information about the Cuis mailing list