Test Plan for Collaborative Server System Prashanth Vijayaraghavan (315) – 380-6069.

Slides:



Advertisements
Similar presentations
Mercury Quality Center 9.0 Training Material
Advertisements

System Administrator Roles in Supporting Site Customizations Lynn Ritger Software Integrations Coordinator, FASTER Asset Solutions.
IOTAP Software Build Process Author: Aman Choudhary Draft Version – Work In Progress.
We have developed CV easy management (CVem) a fast and effective fully automated software solution for effective and rapid management of all personnel.
Task/Incident Tracker Content The Big Picture Design Considerations Scenario Ticket State Model.
Sunday Business Systems Asset Tracking Database Control Calibrated Equipment Manage Preventive Maintenance Maintenance Tracking.
Defect Tracking and Management
Test Execution and Defect management. 2 Module Objectives Introduction to Test Execution Checklist of Test Execution Defect management Defect Classification.
Software Delivery. Software Delivery Management  Managing Requirements and Changes  Managing Resources  Managing Configuration  Managing Defects 
System Center Configuration Manager Push Software By, Teresa Behm.
Project Kick-off 14-Jan-09.
1 RUP Workshop By George Merguerian Senior Partner Business Management Consultants
Mercury Quality Center Formerly Test Director. Topics Covered Testdirector Introduction Understanding the Testdirector Interface. Understanding Requirement.
CSE 784 Software Studio Phil Pratt-Szeliga Fall 2010 Slides Derived From: Dr. Fawcett.
Mitun PatelMXP07U. Organisational structure Top management; this includes the organisation’s general manager and its executives Department managers; this.
Loupe /loop/ noun a magnifying glass used by jewelers to reveal flaws in gems. a logging and error management tool used by.NET teams to reveal flaws in.
Ground Control™ Document Control and Training Manager
Slide 1 of 9 Presenting 24x7 Scheduler The art of computer automation Press PageDown key or click to advance.
Presented By: Shashank Bhadauriya Varun Singh Shakti Suman.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
© 2009 GroundWork Open Source, Inc. PROPRIETARY INFORMATION: Information contained herein is not for use or disclosure outside of GroundWork Open Source,
Using The WDK For Windows Logo And Signature Testing Craig Rowland Program Manager Windows Driver Kits Microsoft Corporation.
N A managed approach to planning and controlling the implementation of complex application software. n A flexible tool kit, designed to support the Project.
TEAM FOUNDATION SERVER (TFS) By Sunny Niranjana Devi. M.
Session 5: Working with MySQL iNET Academy Open Source Web Development.
Customized cloud platform for computing on your terms !
SIUE Injury Tracking System Project Plan. Team Members: Robbie Marsh Robbie Marsh –Project Manager/Webmaster Ken Metcalf Ken Metcalf –Lead Programmer.
Purpose Intended Audience and Presenter Contents Proposed Presentation Length Intended audience is all distributor partners and VARs Content may be customized.
EMI SA2: Quality Assurance (EMI-SA2 Work Package) Alberto Aimar (CERN) WP Leader.
Changing the way you proof for press.. What is InSite? Kodak InSite software is a portal to the prepress environment that lets printers and their customers.
SEIMS SUPPORT N.C. State Board of Elections
Course Presentation EEL5881, Fall, 2003 Project: Network Reliability Tests Project: Network Reliability Tests Team: Gladiator Team: Gladiator Shuxin Li.
Plenary meeting 2015 – Chania - Crete CASCADE Data Services Yusuf Yigini, Panos Panagos, Martha B. Dunbar Joint Research Centre - European Commission.
Statistics Monitor of SPMSII Warrior Team Pu Su Heng Tan Kening Zhang.
EGEE is a project funded by the European Union under contract IST Testing processes Leanne Guy Testing activity manager JRA1 All hands meeting,
XA R7.8 Link Manager Belinda Daub Sr. Technical Consultant 1.
Access Training Linux/Unix Power Broker Access Custom Schema Database Access Customer Training Date: 25-JAN-2005.
Object-Oriented Analysis & Design Subversion. Contents  Configuration management  The repository  Versioning  Tags  Branches  Subversion 2.
RMS Importer Status MACS Week March 2011 PP b-ABR_RMSImporterStatus Angela Brett RMS Importer Status 1.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Okalo Daniel Ikhena Dr. V. Z. Këpuska December 7, 2007.
Agenda  Project Overview  Project Goal & Scope  Estimates  Deadline  Project Environment  Delivery Plan  Project Plan  Team Structure  Risk Analysis.
T Iteration Demo Team 13 I1 Iteration
Timesheet training Version: Introduction Duration: 1.5 hours Purpose: Guide on how to use Timesheet.
NEM201 Week 4 Project Plan Create and complete outstanding items. 01. Front Cover 02. Document details 03. Scope Document 04. Technical Design 05. Creative.
TargetProcess - AGILE Project tracking tool Shashwat Gupta CS
CMSC 2021 Software Development. CMSC 2022 Software Development Life Cycle Five phases: –Analysis –Design –Implementation –Testing –Maintenance.
QC – User Interface QUALITY CENTER. QC – Testing Process QC testing process includes four phases: Specifying Requirements Specifying Requirements Planning.
JRA1 Meeting – 09/02/ Software Configuration Management and Integration EGEE is proposed as a project funded by the European Union under contract.
Scenario use cases Szymon Mueller PSNC. Agenda 1.General description of experiment use case. 2.Detailed description of use cases: 1.Preparation for observation.
Work In Progress Presentation. Orders Alex Thornton.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Event File System A Sample Scenario for Distributed Project Management Takashi Okumura Department of Computer Science, University of.
QA process for Business Catalyst projects.. Starting a project What QA needs to start testing::  Specifications – A detailed description of the product,
E-ISuite Incident Business Workshop May 10, Implementation Review 2016 News and Updates.
Chapter 25 – Configuration Management 1Chapter 25 Configuration management.
Architecture Review 10/11/2004
Project Center Use Cases Revision 2
Project Center Use Cases
Segments Basic Uses: slides minutes
Project Center Use Cases
ShareTheTraining TRR ARB Presentation Team 11
Project Center Use Cases Revision 3
Project Center Use Cases Revision 3
Introduction to Ms-Access Submitted By- Navjot Kaur Mahi
Engineering Processes
Microsoft Visual Source Safe How & Why
LESSON 01 Hands-on Training Execution
This presentation has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational purposes.
9.2 User Acceptance Testing (UAT) Kick-Off
Presentation transcript:

Test Plan for Collaborative Server System Prashanth Vijayaraghavan (315) –

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 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.

Testing Process

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 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

Integration Schedule 85% of test Procedures passed 2 weeks

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

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

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

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

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 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:

Thank You Questions ?