QA Checklist for MapServer 5.0 release

[Stephen Woodbridge]

Steve,

I originally add the message below to the Daniel's request for the 5.0 
freeze delay, but this might be more appropriate to this thread. Or we 
might want a QA column about having documentation.

------- included message -----------

I would also like to comment that I would like to see additional 
developer documentation in rough added but developers of new features, 
especially those that do not have additional feature development work to 
do. While I know the RFC is supposed to help in this areas it is far 
from complete and often not useful from the how to use the feature 
perspective. I think this is critical on multiple fronts:

1) without dev docs you don't know how to use the new features
2) without dev docs you do not know if the features are complete
3) without dev docs you can not put together a test plan
4) without dev docs the doc staff has little to go on to plan their efforts

So what to we need for dev docs?

1) Not polished docs
2) list of new, changed and obsoleted features
3) how to access each feature
4) what options each feature has
5) how to enable each option
6) I'm sure examples would be welcome if you have them or pointers to 
the msautotest cases

-Steve W


Steve Lime wrote:
> Thanks so much for taking the lead on this! Are there going to be
> specific test cases for each column. For example how to test AGG on
> each platform consistently?
> 
> Steve
> 
>>>> On 7/9/2007 at 9:34 AM, in message
>>>> <4692478C.9080109 at mapgears.com>, Normand
> Savard <nsavard at MAPGEARS.COM> wrote:
>> All,
>> 
>> To ensure that we have a good quality release for 5.0 I suggest
>> that we use a similar form that we used for the previous release.
>> It will help us keep track of which features or group of features
>> have been tested during the release cycle.  This list is not an
>> exhaustive list of all features but tries to cover the main parts
>> of MapServer.  As you will see I also added a column for each new
>> feature that will be included to this release.  In this way we will
>> be able to evaluate how much testing is done on each one of them.
>> 
>> I wrote down some names in the form to act as testers but I prefer
>> that experienced users fill this role instead of developers.  So if
>> any experienced user is interested in giving a hand to make our
>> testing effort more valuable, let us know and we'll add your name
>> to the table.
>> 
>> I have added a "QA/Tests Checklist" to the 5.0 release plan at: 
>> http://mapserver.gis.umn.edu/development/release_plans/mapserver_5_0/mapserv
>>  er_5_0_qa_checklist
>> 
>> I will maintain the checklist and coordinate the QA initiative.
>> 
>> If you have any comments do not hesitate to contact me.
>> 
>> Thanks.
>> 
>> Norm