Software Release Testing u Draft document prepared and

  • Slides: 4
Download presentation
Software Release Testing u Draft document prepared and attached to the agenda page for

Software Release Testing u Draft document prepared and attached to the agenda page for this meeting u Explains the testing steps involved, the groups responsible and how they interact u Gives details of the input/output formalities for each step u Shows the mapping onto the testbeds u Developed in conjunction with LCG and testing groups representatives B. Jones– July 2002 - n° 1

Testbeds and Testing Activities “Development” testbed Mware WPs & toolkits WPa tests “Certification” testbed

Testbeds and Testing Activities “Development” testbed Mware WPs & toolkits WPa tests “Certification” testbed Testing Group WPb tests WP dev. & unit tests. Leave testbed stable (auto tests work) WPf tests Loose Cannons “Production” testbed Dist. & install. & grid tests Applications ITeam LCG Certification Auto. & manual tests Office hours System tests Office hours 24 x 7 B. Jones– July 2002 - n° 2

Open Issues u Need n clearer definition of the test steps to be performed

Open Issues u Need n clearer definition of the test steps to be performed by the groups: WP unit tests: test plans documents prepared s Necessary to appoint a person responsible for quality/testing in each WP n ITeam: test plan needed n Testing group: test plan document prepared s http: //edms. cern. ch/document/341943/ n Loose Cannons: tests to verify use cases? n LCG Certification: test plan to be developed u Certification u Production testbed needs to be created in conjunction with LCG testbed needs to be expanded in conjunction with LCG n Open to WP 8, WP 9 & WP 10 n Data. Grid cannot provide 24 x 7 service itself u This n approach will be reviewed after release 1. 4 Full cycle is estimated to take about 4 months (i. e. 3 releases per year on the production testbed) B. Jones– July 2002 - n° 3

Release schedule u EDG 1. 2 being finalised now n Deployed on production testbed

Release schedule u EDG 1. 2 being finalised now n Deployed on production testbed n Used as a basis for GLUE activities (separate testbed) u EDG 1. 3 in July (will not be deployed on production testbed) u EDG 1. 4 : in reality will this become testbed 2? (I. e. October 2002) u Scheduling points to take into account: n Incorporate modifications for GLUE schema: end July 2002 n SC 2002, IST 2002, EU 6 th Framework demos: November 2002 B. Jones– July 2002 - n° 4