[Cuis] Canonical test cases?

[H. Hirzel]

The file testResults.xml which Juan added has

<testcase classname="ApiFile" name="testImagePNG01WriteToFile"
status="passed"/>
<testcase classname="ApiFile" name="testImagePNG02ReadFromFile"
status="passed"/>
<testcase classname="ApiFile" name="testText01WriteToFile" status="passed"/>
<testcase classname="ApiFile" name="testText02ReadFromFile" status="passed"/>

So there is an issue of test setup which was not fullfilled in my case....
Might be a Linux Mint issue (access rights)

On 7/20/15, H. Hirzel <hannes.hirzel at gmail.com> wrote:
> On 7/20/15, Phil (list) <pbpublist at gmail.com> wrote:
>> 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.
>
>
> I loaded the class ApiFile only and I get 3 tests passed and 1 failure
> in Cuis 2.4-2424.
>
> Can you confirm this, Phil?
>
>>> regards
>>>
>>> Hannes
>>>
>>
>> Thanks,
>> Phil
>>
>>
>> _______________________________________________
>> Cuis mailing list
>> Cuis at jvuletich.org
>> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Cuis4.2-2424_Testfiles_on_LinuxMint_Screenshot from 2015-07-20 08:13:48.png
Type: image/png
Size: 36391 bytes
Desc: not available
URL: <http://jvuletich.org/pipermail/cuis_jvuletich.org/attachments/20150720/7a092b24/attachment-0004.png>