RE: Y2K testing

Documents are absolutely required to prove that you have tested your
application before implementation. This helps for further refe. in
future, in case of any problems. But in my view there are no standard
document formats for this purpose. One has to design on their own as per
their need and application concerned or anybody who has done this for a
manufacturing concern should be contacted. Generally these documents
should have the following:

Who has developed the unit/program/module...
Who has tested - Unit/Module
Who has approved , Date etc.
Steps followed
Data used to test
Conditions tested
Results - Screens, Printouts etc
If not passed the tests/conditions, who has done the error analysis
Regression level - This increases till zero defect.

These documents should be made ready once the design phase is over. Test
conditions should have been prepared in parallel with the Code
development. This saves time.

Jai

> ----------
> From:         Steve Raisor[SMTP:sraisor@iglou.com]
> Reply To:     MIDRANGE-L@midrange.com
> Sent:         Friday, September 25, 1998 7:53 AM
> To:   Midrange-L
> Subject:      Y2K testing
> 
> 
>     We are about to start final Y2K testing out our company.  We have
> already made all the database and programming changes we think are
> necessary, tested them, and implemented them in our production
> environment.  The question we discussing is what documentation should
> be produced out of this process for legal, auditing, and customer
> purposes.  We are a manufacturing company.
>     On one side of the discussion, there is the belief that we need a
> document for each of our applications, describing what processes were
> tested, the results, and proof that the testing proved ok(ex.
> printouts), on the other side of the discussion is the belief that a
> general description of the method of testing, the applications tested,
> the general results, but no detailed descriptions of the processes
> tested or detailed results. 
>  
> Any opinions we be greatly appreciated!!
> Steve Raisor
>  
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---