[Testing] test pages in the wiki

[Kim Quirk]

Hi Tim and others,
For bugs, use Trac. I don't recommend putting in bugs for any release after
build 406 right now because they are too much in flux (too many bugs). There
is usually an announcement on devel at laptop.org when there is a stable
release, and you can see the last good release from the front page of the
wiki. As we get closer to a release we'll probably want to take all the
builds.

What we probably need to focus on right now is test planning. If you use
build 406 to see how things work today, we can all write some test cases
that can be executed each time we get a 'stable' build -- and maybe figure
out the best way to automate some of it.

If you want to work on basic Functional tests or Secondary Functional tests
for each Activity, please go right into the Activity from the 'Activities'
page on the wiki and add a 'Functional Test' section (I started this for the
first few activities).

Please feel free to suggest better format, etc.
I would really like to use something for tracking test cases -- Trac?

Thanks,
Kim


On 5/24/07, Tim Reilly <treilly at redhat.com> wrote:
>
> On Thu, 2007-05-24 at 14:43 -0400, Christopher Blizzard wrote:
> > Kim has been working on some pages that define some ideas around
> > testing:
> >
> > http://wiki.laptop.org/go/Test_issues
>
> Now we know what apps (or, err, acts) to focus on, this is great! Should
> we start filing things in trac? Talk about what we're running into on
> olpc? What is the most helpful to you Cambridgians?
>
> tim
>
> _______________________________________________
> Testing mailing list
> Testing at laptop.org
> http://mailman.laptop.org/listinfo/testing
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.laptop.org/pipermail/testing/attachments/20070524/8182a910/attachment.htm