軟件測(cè)試-testplan.doc

12020 2 8 Test Plan Project Prepared by Date Product Version TEMPLATE 22020 2 8 Table of Contents OVERVIEW 3 1 0 SCOPE 3 1 1ASSUMPTIONS 3 1 2 PREREQUISITES 3 1 3 SYSTEM REQUIREMENTS 3 1 4 TERMS AND DEFINITIONS 4 1 5 RELATED DOCUMENTS 4 SECTION 2 PRODUCT AREAS TO TEST 5 2 1CLIENT TESTING 7 2 1 1 Configuration Parameter 8 2 4 11Next section here 8 SECTION 3 ISSUES 9 SECTION 4 QA S PROJECT ESTIMATES 10 SECTION 5 SQA ROBOT SET UP FOR BOUNDARY TESTING 11 SECTION 6 CHANGE HISTORY 12 32020 2 8 Overview This document will be divided up into the following section Section 1Scope Section 2Product Areas to Test Section 3Issues Section 4Project Estimates Section 5 SQA Robot Instructions for testing Section 6 Change History 1 0 Scope This test plan lists how the QA department will test the Project The intended audience for the document includes management and employees of YOUR COMPANY and all parties directly involved with the project This test plan is a work in progress document that will modified and appended to during the testing process 1 1Assumptions It is assumed that the Oracle database will be set up and installed correctly 1 2 Prerequisites Client Application Database server on a single database The process to be loaded on the server and configured appropriately 1 3 System Requirements Client Windows 95 Server AIX NT 4 0 for initial testing 42020 2 8 1 4 Terms and Definitions QA Quality Assurance Department Also can be used as a term when referring to testing Positive Functionality Testing will verify that each modules basic functionality is working Boundary Stress Testing will verify the upper and lower limits set on any item within the module This will consist of using Min Values Min Values 1 Max Values 1 and Max Values Error Negative Testing will verify that the invalid entries command and actions in the module are handled correctly Integrated Testing will verify that if entries in the component under test cause changes in other areas and that those areas are correctly changed Unit Test This is a test that the development team will do before handing over the finished code to QA System Test The test phase where the product is test thoroughly 1 5 Related Documents The following files can be found on the machine NameType Section 2 Product Areas to Test In order to ensure that the entire interface is tested completely it will be broken down into the following components Client Testing Database Testing Executable Testing and File Testing Testing Summary This table is a list of all the tests in the test plan It also prioritizes the order in which the tests need to be executed in A number of the test cases can be done simultaneously It is also important that the tests run is the order they are listed in the table Test SectionNumber of tests PassFailedCompleted Date Issue Numbers Functional Testing 2 3 1 13 1 2 1 1 7 2 1 2 2 2 1 3 1 2 3 4 1 1 52020 2 8 2 1 4 14 2 2 1 9 2 2 2 2 Error Testing 2 1 4 Payment19 2 1 1 Configuration Parameters6 2 1 2 External Interface1 2 1 3 Data9 2 3 1 Executable running7 2 4 4 Detail Record File Format9 Boundary 2 1 1 Configuration Parameters2 2 1 4 Payment20 2 3 1 Executable running1 2 4 4 Detail Record File Format23 2 4 6 Batch Trailer File Format1 2 4 7 Trailer File Format2 Do this section last Functional 2 1 5 Sales Order10 2 3 5 PO2 2 4 11 Receipt3 Error Testing 2 1 5 SALES17 Boundary Testing 2 1 5 Sales 13 Integration 2 1 4 Payment2 2 1 5 Order2 2 4 10 Verify data in reports2 TOTAL262 2 1Client Testing In the Client Testing section testing will focus on the areas of the product that are used to configure and create the necessary data for the executable More details here The areas of the client that will be tested are Configuration Parameters External Interface Data Window s Payment Section Payment Window to create the necessary data Sale Order Window to create the necessary data Setup requirements for Client Testing 62020 2 8 TaskDone 1 Determine if this needs to be tested on a single or distributed database 2 Set up area on system 3 Setup up a market on database 4 Set up Store Locations in the market add all set up data 2 1 1 Configuration Parameter Functional Testing test cases Note add any notes here Test Test ProcedureResults Pass Fail 2 1 1 1 2 1 1 2 2 1 1 3 2 1 1 4 2 1 1 5 2 1 1 6 2 1 1 7 Boundary and Stress Testing Test cases Test Test ProcedureResults Pass Fail 2 1 1 8 2 1 1 9 Error Negative Testing Testcases Test Test ProcedureResults Pass Fail 2 1 1 10 2 1 1 11 2 1 1 12 2 4 11 Next section here Integration Testing test cases Test Test ProcedureResults Pass Fail 2 4 11 1 2 4 11 2 2 4 11 3 72020 2 8 Section 3Issues List your issues here 1 2 3 Section 4QA s Project Estimates Test Planning Writing the test design document 1 day Writing the test plan document5 days Review by team day Finalized version of the documents day Set up environment and sqa robot scripts1 day Test Phase 1 System Test Execution of all the test cases in the test plan 4 days Work with developer1 day Test Phase 2 Final Test Execution of all the test cases in the test plan 4 days Total17 Days Note This figure represents pure testing time It is not actual work days 82020 2 8 Section 5 SQA Robot Set up For Boundary Testing A project has been created in the repository for the boundary testing Files used in Robot XXXXXXX sbh to be put in the sqbas32 directory on PC XXXXXX sbh to be put in the sqbas32 directory on PC Bound1 rec shell script for Payment topic testing Bound2 rec shell script for order topic testing Openconv the script that opens up application Opencsh the script that opens up a draw payment the script that does the payment Saleap the script that does the order Clapcsh the script the closes the draw Closecon the script that closes down application Steps to execute 1 Set workstation to the appropriate store location 2 Make sure there are no draws open in the store 3 Create a customer for that location in customer topic 4 Bring up XXXXXX sbh file to edit the following variables