Test Plan for

Collaborative Server System

Prashanth Vijayaraghavanpvijayar@syr.edu(315) – 380-6069

Agenda

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

Objectives of testing the systemThe 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.

Testing ProcessReview B SPEC

Write Test Descriptions

And Test Procedures

Integrate Modules

AndRun Test

Procedures

Fix Bugs

Execute Qualification

Test

Deliver Product

Fix errors in test procedures

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.

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.

Schedule and Resource allocation

Activity Description RI Start Date End DateProject start Everyone 9/24/07 12/10/07A-Spec review Sreevatsa 10/1/07 10/1/07Analyze A-Spec Everyone 10/2/07 10/6/07Update A-Spec Sreevatsa 10/8/07 10/8/07B-Spec Review Team Leaders and members 10/15/07 10/15/07Analyze B-Spec Test Team, SA, PM 10/16/07 10/18/07Update B-Specs Team Leaders and Architect 10/18/07 10/20/07Test 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 ShahEstepan MeliksetianFalgun ShahVijay ReddyPrashanth VSunny GuptaPrashanth VSunny GuptaVijay Reddy

10/16/0710/29/0710/29/0710/16/0710/16/0710/29/0710/16/0710/16/0710/16/07

11/5/0711/8/0711/8/0711/5/0711/5/0711/8/0711/5/0711/5/0711/5/07

Test Procedure Review Prashanth, SA,PM, Customer 11/5/07 11/10/07Running test procedure Prashanth V, Test Team 11/11/07 11/24/07Test Readiness Review Prashanth V and Test team 11/26/07 11/26/07

Integration Schedule

85% of testProcedures

passed

2 weeks

Whiteboardtool

Nov 8th

23 days

Wiki toolNov 5th

Progress Monitor Tool

Nov 3rd

Team Structure

toolNov 1st

Data ManagerOct 31th

Comm andExec

IntegrationOct 29th

CompleteComm moduleOct 27th

CompleteExecutivesOct 27th

StartOct 16th

11 Days

13 Days 15 days 16 days 17 days 20 days

Integration DetailsDescription RI Completion Date

Complete Unit test and ensure integration preparedness for communication module

Comm team 10/27/07

Complete unit test and ensure integration preparedness for client executive and server executive.

Executive team 10/27/07

Integration of Communication module and executives

Prashanth V,Sunny Gupta, Vipul, Rajesh.

10/29/07

Bug Fixes and testing Sunny, Prashanth, Vijay 10/27/07Complete 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 Testing Heidi, 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 PMT Team leaders, Vijay, Prashanth. 11/1/07

Integration of TST Team Leader, Prashanth , Falgun 11/3/07

Bug fixes and testing Falgun, Abhishek 11/7/07

Integration Details( Cont..)

Complete Unit test and integration preparedness for Wiki

Wiki team. 11/4/07

Wiki integration Kedar, Sunny, Prashanth. 11/5/07

Bug Fixes and testing Prashanth, Rajesh, kedar 11/10/07

Complete Unit test and integration preparedness for whiteboard tool

Whiteboard team 11/8/07

Whiteboard integration Shrenik, Estepan, Aniruddha, Prashanth, Sunny.

11/9/07

Bug Fixes and testing Sunny, Aniruddha, Shrenik 11/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 testing Test Team, Team leaders 11/20/07

Bug Fixes Team leaders, Test Team 11/22/07

Test procedure execution Test Team 11/25/07

Test readiness Test Team 11/26/07

Network ShareServer Name: Ecshome1Project Root Directory: \\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

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)

TestPlanTestProcedures

TeamStructure (Full – Abishek allen)Source CodePresentationsTest

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

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.

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

Thank You

Questions ?