1. Test Plan for Collaborative Server System Prashanth Vijayaraghavan pvijayar@syr.edu (315) – 380-6069

2. Agenda Objectives of Qualification testing. Testing Process. Responsibilities. Schedules and Resource allocation. Integration schedule. Share and Repository (version control). Managing Bugs and errors.

3. Objectives of testing the system The intend is to prove that: It Meets all the requirements in A-spec and B- spec. It Meets the standards required by the customer. The software is of high quality. - Robust. - Simple and flexible.

4. Testing Process

5. Test Types and Responsibilities Unit Test: RI : Developers and Team Leader. Integration Test: RI: Integration of 2 sub systems – Team leads from the 2 sub systems. Track Bugs & errors – Assigned Test Members.

6. Test Types and Responsibilities (Cont..) Qualification Test: Designing a test plan – Test Team. Writing Test procedures – Assigned test team members with help from team leads. Develop Pass/Fail Criterion – Test team member with help from Team Lead. Test Procedure review – Team lead, TSM, PM, SA and Customer. Dry Run of Test procedures – Test team. User acceptance and sign off – Customer, PM,TSM. Eating our own Dog food RI : Entire CSERV team. Eg – Work packages for our tools, Our team structure.

7. Schedule and Resource allocation Activity DescriptionRIStart DateEnd Date Project startEveryone9/24/0712/10/07 A-Spec reviewSreevatsa10/1/07 Analyze A-SpecEveryone10/2/0710/6/07 Update A-SpecSreevatsa10/8/07 B-Spec ReviewTeam Leaders and members10/15/07 Analyze B-SpecTest Team, SA, PM10/16/0710/18/07 Update B-SpecsTeam Leaders and Architect10/18/0710/20/07 Test Description and procedure preparation. -Team Structure tool.------------- - Work Package tool.------------- - Scheduling tool.------------------ -Progress Monitor Tool.---------- -Wiki Tool.--------------------------- - Whiteboard Tool.---------------- -Communication.------------------ - Data manager.------------------- - Client and server executives.- Falgun Shah Estepan Meliksetian Falgun Shah Vijay Reddy Prashanth V Sunny Gupta Prashanth V Sunny Gupta Vijay Reddy 10/16/07 10/29/07 10/16/07 10/29/07 10/16/07 11/5/07 11/8/07 11/5/07 11/8/07 11/5/07 Test Procedure ReviewPrashanth, SA,PM, Customer11/5/0711/10/07 Running test procedurePrashanth V, Test Team11/11/0711/24/07 Test Readiness ReviewPrashanth V and Test team11/26/07

8. Integration Schedule 85% of test Procedures passed 2 weeks

9. Integration Details DescriptionRICompletion Date Complete Unit test and ensure integration preparedness for communication module Comm team10/27/07 Complete unit test and ensure integration preparedness for client executive and server executive. Executive team10/27/07 Integration of Communication module and executives Prashanth V, Sunny Gupta, Vipul, Rajesh. 10/29/07 Bug Fixes and testingSunny, Prashanth, Vijay10/27/07 Complete Unit test and ensure integration preparedness for Data manager module and database Data manager Team.10/26/07 Integration of data manager with executives DM team, Prashanth.10/31/07 Bug Fixes and TestingHeidi, Vikram, Prashanth, Sunny.11/4/07 Complete unit test and integration preparedness for progress monitor tool and Team structure tool TST team, PMT team.10/31/07 Integration of PMTTeam leaders, Vijay, Prashanth.11/1/07 Integration of TSTTeam Leader, Prashanth, Falgun11/3/07 Bug fixes and testingFalgun, Abhishek11/7/07

10. Integration Details( Cont..) Complete Unit test and integration preparedness for Wiki Wiki team.11/4/07 Wiki integrationKedar, Sunny, Prashanth.11/5/07 Bug Fixes and testingPrashanth, Rajesh, kedar11/10/07 Complete Unit test and integration preparedness for whiteboard tool Whiteboard team11/8/07 Whiteboard integration Shrenik, Estepan, Aniruddha, Prashanth, Sunny. 11/9/07 Bug Fixes and testingSunny, Aniruddha, Shrenik11/15/07 Complete unit test and integration preparedness for work package tool and scheduling tool WP team and Scheduling team.11/10/07 Integration of work package tool. Estepan, Prashanth, Sagnak, Kimberly 11/11/07 Integration of Scheduling tool Estepan, Prashanth, Adithya and Kamarish 11/13/07 Complete product testingTest Team, Team leaders11/20/07 Bug FixesTeam leaders, Test Team11/22/07 Test procedure executionTest Team11/25/07 Test readinessTest Team11/26/07

11. Network Share Server Name: Ecshome1 Project Root Directory: \\Ecshome1\784Project$\CSE784FinalProjF07\\Ecshome1\784Project$\CSE784FinalProjF07 Steps to access the above network share. -Login into a ECS cluster. -Open my Network places from desktop. -Click add network place from the left tab. -Follow the wizard and enter network address for which you have permissions. Eg: Test team member can enter \\Ecshome1\784Project$\CSE784FinalProjF07\TestTeam

12. Network Share structure CSE784FinalProjF07 (R&W -PM,SA) ASPECReview (R -team leads) BSPECReview (R&W -team leads) CSPECReview (R&W -team leads) TestReadinessReview (R&W -test team members) TestTeam (R&W- test team members) TestPlan TestProcedures TeamStructure (Full – Abishek allen) Source Code Presentations Test WorkPackage (Full – Kimberly Lang) Scheduling (Full – Adithya Dhamani) ProgressMonitor (Full – Abhinav Bose) Wiki (Full- Kedar Joshi) WhiteBoard (Full – Aniruddha Gore) Comm (Full – Rajesh) DataManager (Full – Heidi Salapong) Executives (Full – Sreevatsa) LatestBuild (R – Team leads) QualsBuild

13. Repository with version control Version control software – Sub version Server – Apollo server running on unix. Client – Win32 application installed in some machines in link 202. Rules: -The products which are used for integration must be checkout from repository. -Each build after integration must go into the repository -Final qualification build must come from the server.

14. Software Change request form Name (Originator): Title: Start date and End Date: Priority: Status: (open or closed ) Assigned team: Assigned member: Affected file names: Statement of problem: Solutions:

15. Thank You Questions ?