[Testing] Community-based testing of OLPC activities

[Grig Gheorghiu]

I think it can be done with some creative additions to:

* 'type' of issue (e.g. 'test case')
* 'milestone' (e.g 'version A.b.c.d')
* resolution value (e.g. 'works in version A.b.c.d' or 'fails in
version A.b.c.d)

So let's say you want to define a new test case. You create a new
issue,  set its type to 'test case', give it a milestone of 'version
A.b.c.d', then assign it to a tester.

The contents of the issue would be the actual test case steps.

The tester would go through the test case, and mark it as 'works in
version A.b.c.d' or 'fails in version A.b.c.d', together with comments
as to why it fails for example.

A little contrived, but it can be made to work :-)

Grig 


--- Kim Quirk <kim.quirk at gmail.com> wrote:

> hmmm... so how would we use that for test case mgmt?  Maybe we should
> to run an example test case.
> 
> Are you thinking of a 'test case' component? Or something else?  How
> would we get reports and/or designate test runs?
> 
> Kim
> 
> 
> On Nov 7, 2007 5:55 PM, Grig Gheorghiu <grig at gheorghiu.net> wrote:
> > Well, Trac supports the creation of issues/tickets out of the box.
> > That's what I was referring to, not necessarily the test manager
> > plugin.
> >
> > Grig
> >
> >
> > --- Kim Quirk <kim.quirk at gmail.com> wrote:
> >
> > > Yes... we did ask Danny (our Sysadmin) to try and load the 'test
> case
> > > manager' Trac extension and there were issues. I think it was SVN
> > > based or something(?). I thought that would be the quickest path
> to a
> > > test case mgmt system.
> > >
> > > Copy Danny - do you remember what the issues were with the trac
> > > extension?
> > >
> > > Thanks,
> > > Kim
> > >
> > >
> > > On Nov 7, 2007 5:03 PM, Grig Gheorghiu <grig at gheorghiu.net>
> wrote:
> > > > --- Kim Quirk <kim.quirk at gmail.com> wrote:
> > > >
> > > > > Hi Greg,
> > > > > Thanks for putting this together. I think the matrix of test
> > > plans is
> > > > > a good idea. We had tried to create something like this at
> > > > > http://wiki.laptop.org/go/User_Stories_Testing site. Yours is
> a
> > > more
> > > > > friendly and probably easier to use, so it would be great if
> you
> > > can
> > > > > incorporate your look/style with the test plans and info that
> are
> > > > > there.
> > > > >
> > > > > My biggest issue with a wiki based test case management
> system is
> > > > > that
> > > > > you can't easily track results. Test cases are rarely run
> once --
> > > but
> > > > > need to be run many times after pretty much any code changes
> that
> > > > > might affect it. If there is some way to hook this 'result'
> page
> > > into
> > > > > a test case management database, then we would get the best
> of
> > > both
> > > > > worlds. Easy update, easy run and good reporting on a wiki
> page.
> > > > >
> > > >
> > > > How about using Trac as the wiki dedicated to testing? Trac
> does a
> > > > fairly good job as a ticket/issue tracking database. And
> there's
> > > > support for linking bugs/issues very easily within wiki text.
> > > >
> > > > Grig
> > > >
> > >
> >
> > _______________________________________________
> > Testing mailing list
> > Testing at lists.laptop.org
> > http://lists.laptop.org/listinfo/testing
> >
>