Tm test plan template university 0 2 (1)

TM Test Plan Template Content 41 Introduction 41 1 Purpose 41 2 Scope 41 3 Definitions and Abbreviations/Acronyms 41 3 1 Definitions 41 3 2 Abbreviations/Acronyms 41 4 Users of the Document 42 Referen[.]

Content Introduction 1.1 Purpose 1.2 Scope .4 1.3 Definitions and Abbreviations/Acronyms .4 1.4 1.3.1 Definitions 1.3.2 Abbreviations/Acronyms Users of the Document References and Related Documents .4 Schedules and Milestone .4 Resource Requirements 4.1 Hardware .4 4.2 Software 4.3 Tools used for Testing 4.4 Test Environment 4.5 Staffing 5 4.5.1 Roles and Responsibilities 4.5.2 Training Test Scope .5 5.1 Features to be tested .5 5.2 Features not to be tested .5 Test Strategies .5 6.1 6.2 Test Stages 6.1.1 System Testing 6.1.2 Acceptance Testing Types of Testing 6.2.1 6.3 Functionality Testing Other Testing .10 6.3.1 Hot Fix / Patch Testing 10 6.3.2 Data-Migration Testing 10 Acceptance Criteria 10 Defect Tracking 10 8.1 Defect Classification 10 8.2 Defect Life Cycle 10 Test Deliverables 10 9.1 Test Cases 10 9.2 Test Reports 10 Introduction 1.1 Purpose To test some functions followed of Youtube service : _ Youtube account _ Uploading and deleting video files _ Discussing on video files _ Search 1.2 Scope This section to provide test requirement as below : _ Browsers : Google Chrome, IE 8, Firefox 11 _ Using application : Adobe Flash Video Features and functions need testing : Youtube account: a Creating a new account b Modifying account infomation c Login in system Uploading video files: a Uploading a video file b Deleting a video file Discussing on video files : a Posting comment b Modifying comment c Deleting comment d Replying to other’s comment Search a Basic search b Advanced search 1.3 Definitions and Abbreviations/Acronyms [Define the required definitions and Abbreviations /Acronyms] 1.3.1 Definitions Terms Definition 1.3.2 Abbreviations/Acronyms Abbreviation / Description Acronyms IE Internet Explorer 1.4 Users of the Document _ Test Designers _ Testers References and Related Documents [Documents related to the project which will be useful for delivering the project with quality] Schedules and Milestone Milestone Deliverables Duration Start Date End Date Generating testcases days June 15 2012 June 17 2012 Executing Test day June 18 2012 June 19 2012 Report and summary day June 20 2012 June 20 2012 Resource Requirements 4.1 Hardware Minimum system : Intel Pentium 4, Ram 256Mb, VGA onboard 256 Mb 4.2 Software Adobe Flash Video Google Chrome IE Firefox 11 4.3 Tools used for Testing _HP Quality Center : for storing Test cases, Defects and Test cases status 4.4 Test Environment Operating : Windows 7, Windows XP Browsers : Google Chrome, IE8 , Firefox 11 4.5 Staffing [Mention staffing details of this Project, this includes Roles and Responsibilities of each individual and the Training Details] 4.5.1 Roles and Responsibilities Worker Roles Do Quoc Dat Test Leader Responsibilities Build test plan Management reporting Pham Duc Xuan Test Designer Generate testcases Evaluate effectiveness of test effort Ho Minh Vuong Tester Execute test and log results for function: _ Creating account _ Modifying account _ Deleting account Dang Van Xuyen Tester Execute test and log results for function: _ Uploading video files _ Discussing on video Files Nguyen Anh Tuan Tester Execute test and log results for function: _ Search 4.5.2 Training Not required Test Scope 5.1 Features to be tested [List out all software features and combinations of features that will be tested in this project.]      Creating a new account Modifying account infomation Login in system Uploading a video file Deleting a video file       Posting comment Modifying comment Deleting comment Replying to other’s comment Basic search Advanced search 5.2 Features not to be tested [List out all the features and significant combinations of features which will not be tested in this project.] Test Strategies We understand Youtube with role of a user without knowing code lines to make it Therefore, we just need to implement System Testing and Acceptance Testing, Functionality Testing (using Black Box) Unit Testing - This test will not be implemented or executed This test is not appropriate Integration Testing - This test will not be implemented or executed This test is not appropriate Regression Testing - This test will not be implemented or executed This test is not appropriate Security And Access Control Testing – It’s really unnecessary 6.1 Test Stages 6.1.1 System Testing Inputs/ Entry Criteria Automation Tool Used No Suspension Criteria There are some Fatal errors in smoke test build without work around solutions Resumption Criteria Any fatal errors with work around solutions Outputs/Exit Criteria 100% of test cases have been executed and passed Responsibility Testers execute test and log results (Developer / tester / Customer, etc) How to perform (Manual / automated , etc) Manual When to perform (During interim build / iteration release / project release, etc) During interim build 6.1.2 Acceptance Testing Inputs/ Entry Criteria Automation Tool Used No Suspension Criteria No Resumption Criteria No Outputs/Exit Criteria When the evaluation of users is enough requirement Responsibility (Developer / tester / Customer, etc) How to perform Manual (Manual / automated , etc) When to perform Project release (During interim build / iteration release / project release, etc) 6.2 Types of Testing 6.2.1 Functionality Testing Inputs/ Entry Criteria Automation Tool Used No Suspension Criteria • No build notes or it is not clear • There are some Fatal errors in smoke test build without work around solutions Resumption • Build notes clearly Criteria • Any fatal errors with work around solutions • Test cases had been baselined Outputs/Exit Criteria 100% of test cases have been executed and passed Responsibility Testers execute test and log results (Developer / tester / Customer, etc) How to perform (Manual / automated , etc) Manual When to perform (During interim build / iteration release / project release, etc) Iteration release 6.3 Other Testing 6.3.1 Hot Fix / Patch Testing 6.3.2 Data-Migration Testing Acceptance Criteria _ 100% of test cases have been executed and passed _ Stability requirements have been met Defect Tracking 8.1 Defect Classification  Critical –  High –  Medium –  Low - 50 8.2 Defect Life Cycle [Mention the defect life cycle in this project from defect reporting to defect closure.] Test Deliverables 9.1 Test Cases Test Cases.xls ( attached ) 9.2 Test Reports [Provide link to the Test Reports/Test Metrics generated for this project here]