[Testing] Call for help for testing specific items

[Daniel Drake]

Hi,

Thanks for the excellent testing reports of 11.2.0 images, hopefully
this will continue :)

We do really benefit from the fresh, unguided perspectives people take
on testing so please do not stop doing this.

However, if you do want to help directly with some pending QA tasks
for OLPC, we do have some specific items that need testing.

We have a QA process where once we make a fix to a specific ticket
regarded as important, we get our QA staff (Sam) to verify the fix.
Unfortunately Sam is a bit overloaded and we have a backlog of tickets
in this state.

So, we could do with your help verifying the fixes to the following tickets:

http://dev.laptop.org/query?status=assigned&status=new&status=reopened&col=id&col=summary&col=milestone&col=status&col=type&col=priority&col=component&next_action=test+in+build&group=component&max=400&order=priority&milestone=11.2.0-M1&milestone=11.2.0-M2&milestone=11.2.0-M3&milestone=11.2.0-M4&milestone=11.2.0-final

shorter version of the URL: http://tinyurl.com/5rkczey

The process is simply: take a ticket, read through it so that you
understand what the original problem was, then attempt to verify the
fix.

This should all be done on the latest build (currently 11.2.0
candidate build 870), even if the ticket suggests testing on an older
one (which was simply the newest one at time of writing).

When done, please either comment directly on the ticket with your test
results, or if easier, write a mail to this list combining the test
results from various tickets.

Some tickets might be hard to test without specific situations, or
might lack clarity on how to test them - in those cases feel free to
either ignore the ticket, or add a comment saying something like "I
don't understand how to verify, simple test case needed".

In response to your comments we will swiftly close the tickets, unless
we deem that further testing is needed.

Note that the above URL is dynamic, so this list will change over the
next month as tickets get verified and as other tickets get solved
(and hence need verifying). So this is an activity that could be
incorporated on a weekly basis to the test group meetings.

Thanks,
Daniel