[Qgis-developer] Quality assurance

[Nathan Woodrow]

I guess the next thing to do would be to work out some list of testers,
what they are testing and a checklist that can be used to check against
each build/release.  The wiki would be a good place to list the testers and
the what area is being tested, I'm not sure that the checklist of "it works
or not" would be good in the wiki.

For me, this kind of user testing needs to be reported on a easy to edit
and use system.   I did find a checklist program for redmine[1] which you
could have with a list of things to check off for each release, or you
could use something like Google Docs and have a spreadsheet with columns:
Feature | Version X.x | Current Build | Comments with the rows having
values like: working; broken; N/A etc.

You could then have:

Print Composer

Feature | Version 1.7.3 | Current Build | Comments
Printing | Working        | Broken          | See issue #xxxx for notes
Legend |  Working        | Working        |
...
...

Thoughts?

Apparently there are things out there that handle this kind of user testing
but I have found any open source/free ones that look good.

- Nathan



[1]  http://redminecrm.com/projects/checklist/wiki/Wiki?version=5

On Mon, Dec 19, 2011 at 7:33 PM, Giovanni Manghi
<giovanni.manghi at gmail.com>wrote:

> On Mon, 2011-12-19 at 10:20 +0100, Andreas Neumann wrote:
> > +1 - I would also be willing to take responsibility as a tester. I
> >  could do the "Print Composer" testing.
>
>
> I also subscribe and as I said I know two other persons (not members of
> this list, but heavy QGIS users) that are willingly to subcribe too.
>
> cheers
>
> -- Giovanni --
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/qgis-developer/attachments/20111219/db34e333/attachment.html