[olpc-nz] Today's/Tonight's QA Phone Call Conclusions & Unofficial Minutes

[Tim McNamara]

On Fri, Feb 26, 2010 at 10:27 PM, Tom Parker <tom at carrott.org> wrote:

> On Thu, 2010-02-25 at 07:56 +1300, Tim McNamara wrote:
>
>
> >  I would love there to be one webpage for test
> >  requests that has some
> >  visual indicator of how many people testing it
> >  and how close to
> >  finished testing it is, with a big tick next
> >  to it when it has been
> >  tested thoroughly.
>
Something as "simple" as a tracker would work. If you want something
> tested, raise a ticket. Developers can look at the ticket to see what
> the status of your test request is. Testers can look at the list of open
> tickets to see what is ready for testing. Every request has a date and a
> log of what has been done. This is how the test groups work in the
> software development houses I've worked with.
>

This is worth investigating. Properly written test cases & test requests
will solve these issues. What do we test today? What has been taken up by
other groups when that email came through to x, y, z list? What methodology
do Activity developers want used?

Bug/ticket triaging becomes significant.. because these reports are not
bugs.

I sense this may place unnecessary burden on developers over time. First of
all, it creates noise in the tracker. Secondly, devs will need to create a
new ticket for the next version of whatever component, but the test cases
remain the same. They just want they tests replicated for a new update. At
every release of a new activity, what set of functionality should be tested
to ensure consistency between releases?

I like the fact that we don't need much more infrastructure, but don't know
how practical things will be in the medium term.

-Tim.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/olpc-nz/attachments/20100227/a2ad637c/attachment.htm