[Cuis] Canonical test cases?

[H. Hirzel]

Other idea: Regularily (e.g. bimonthly) export all the methods (plus
comment) which contain 'test' and 'API' to a markdown file in the
'Documentation' folder.

Check the comments from time to time and generate issues to ensure the
comments are instructive.

We need a process which is quite verbose and which allows us to jump
in after long periods of inactivity and immediatly do something
productive. i.e. enough provide enough context for the activities to
do next.

On 2/23/15, Ken.Dickey <Ken.Dickey at whidbey.com> 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?
> --
> -KenD
>