My task for the next ~6 months

[Samuel Greenfeld]

In my view, the big questions in that thread were (1) what are we trying to
accomplish with a test day and (2) if we need to have test cases for test
days in the first place.

OLPC has a set of test cases in their Wiki, but's a bit stale, and the
current implementation makes them hard to go through.

I could write a set of Sugar test cases for Fedora purposes, but then I
would have to justify spending the time to my boss for doing so.

In general I don't want to have test cases scattered all over the place, as
Sugar information already is found in at least three Wikis, with developers
only tending to update one or two.

(An interesting take on this can be seen in the opening speech of last
year's Google Test Automation Conference, titled 'Test Is Dead' -
http://www.youtube.com/watch?v=X1jWe5rOu3g .  My personal view is that
while the extremes are interesting, I've read books talking about both, and
the truth is somewhere in-between.)


2012/2/20 "Jóhann B. Guðmundsson" <johannbg at gmail.com>

> On 02/20/2012 09:56 PM, Samuel Greenfeld wrote:
>
>> ng test day:
>>
>> http://lists.laptop.org/**pipermail/testing/2012-**February/002609.html<http://lists.laptop.org/pipermail/testing/2012-February/002609.html>
>>
>> In general, it might be useful to know how skilled most test day
>> participants are at testing, as well as the test approach preferred by the
>> Fedora project as a whole when planning these events.
>>
>
> Always assume they don't possess any knowledge et all as in write spoon
> feeding  test direction/cases since the tester might be taking his first
> step within the QA community.
>
> It wont bother those of us that are experienced but it helps those that
> are not thus by doing so you get maximum participation and the widest
> coverage...
>
> A while back I proposed having the test case structure split by
> experience/difficult levels.
>
> JBG
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/test/attachments/20120220/daad0742/attachment.html>