1 / 15

Test Plan for Collaborative Server System

This document outlines the qualification testing objectives, processes, responsibilities, and schedules for the Collaborative Server System. It aims to meet all specified requirements and quality standards as outlined in A-spec and B-spec. The testing process involves unit, integration, and qualification tests, each with clear responsibilities assigned to team members. Key resource allocation and an integration schedule are specified to ensure timely completion of testing activities. Additionally, a version control framework is established for effective management of test procedures and bug tracking.

shayna
Télécharger la présentation

Test Plan for Collaborative Server System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Test Plan forCollaborative 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

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

  9. Integration Details

  10. Integration Details( Cont..)

  11. Network Share • Server Name: Ecshome1 • Project 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

  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 ?

More Related