Fw: [cosmos-dev] project process, test pass exit criteria..

[Toni Drapkin <tdrapkin@xxxxxxxxxx>]

Gentle reminder:  please respond
if you think this is a good starting point for us to use or if you have
another suggestion.    We'll review the input at next weeks community
call.    Thank you!   

Regards,   Toni 
Program Director, 
Tivoli Open Standards & Open Source
tdrapkin@xxxxxxxxxx
(919)254-5224 / t/l 444-5224
(919)815-9894 - cell phone

Valentina Popescu <popescu@xxxxxxxxxx>
Sent by: cosmos-dev-bounces@xxxxxxxxxxx

05/31/2007 05:27 PM

Please respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx>

To	cosmos-dev@xxxxxxxxxxx
cc
Subject	[cosmos-dev] project process, test pass exit criteria..

Hi everybody 

I promised to find and attach the TPTP process documentation around testing
and test pass exit criteria, all these to be used as a starting point (
or probably just as a sample ) for the COSMOS development process 

The link below gets you to a TPTP committers documentation where various
things are documented ( development process, writing design documents,
test process ). The Testing section under this link will get you to a set
of documents describing how to create, run, check in and report testcases
and test results using the TPTP infrastructure ( to be used if we decide
to make use of the TPTP testing framework ) 

http://www.eclipse.org/tptp/home/documents/committers.php


Regarding the test process - exit criteria.  The only link I could
quickly find for the testpass exit criteria is our release plan

http://www.eclipse.org/tptp/home/project_info/releaseinfo/4.4/Eclipse%20TPTP%204_4%20Release%20Review.ppt

( page 13, see release exit criteria ) 

As for the release schedule and the testpass cycle, this is a process that
is updating and improving as we gain experience and learn from past releases.
It is also based on the input from project leads on the amount of time
required to run a testpass; in the TPTP case, since we test against multiple
platforms and have about 9k testcases ( junit, manual, automated ) we had
approximated that we need one week for a full test pass; also decided to
have two test pass weeks per iteration, first week full test pass and second
validating defects fixed in the first week. - hope this helps..

Thank you,
Valentina Popescu
IBM Toronto Labs
Phone:  (905)413-2412         (tie-line  969)
Fax: (905) 413-4850_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev