[software test series vi] software system test scheme

​

 

Software system test plan

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Program name ：​

  Production unit ：​

  Executive unit ：​

  The date of the report ：​

Revision records

Version identifiers	notes Interpretation of the	do person	Japan period

Document usage object

surname name	job   service

 

Vetting staff

surname name	job   service	Japan period

1． Document identification

This document contains information for [ Production unit ] Developed [ Name of product to be tested ] Comprehensive test plan .

2． Summary

2.1 Document purpose

This document is to complete [XXX] Guiding documents for project testing . This document gives the requirements for testing 、 Test environment 、 General requirements for test process and test results , This is also the basis for writing other documents and evaluating the results in this test project .

2.2 Test purpose

The purpose of this test is explained here .

[ Example ：

This test is for [xxx] Confirmation of project / Identification of / check before acceptance / entrust / Registration test , The purpose is to determine whether the system meets 《 Requirements specifications 》 Provide objective basis for the function and performance indexes specified in .]

2.3 Test range （ The appropriate test scope and content can be selected according to the actual situation of the company's system ）

reference [ Project name ] Contract and requirements documents , The scope of the test is described here , List the types and contents to be tested .

[ Test project ] Test range			The first 1   page	common 2 page
Serial number	Test categories	Test content
1	A functional test	Such as ： menu , The toolbar , Shortcut key , Drop down box, etc
2	Interface tests	Such as ： Login screen , General interface , Report interface, etc
3	tolerance test	Such as ： Data length , data type , Illegal operation, etc

4	xxx	xxx
5

 [ Example ：

This test is a software validation test , Including software 、 Functionality 、 Interface property 、 Fault tolerance characteristics .

2.4 Test environment description

Test environment and configuration information for the application under test , Here is a brief description .

Software environment ：

Terminal category ​	operating system	Related application software
Server side
client

 

Hardware environment ：

Terminal category ​	machine name	Equipment serial number ​	Configuration instructions ​
Server side
client

The network environment ：

Network type ​	bandwidth ​	equipment ​	Number ​

 

Other auxiliary equipment ：

 

Equipment name ​	Specifications and models ​	Number ​	remarks ​

 

2.5 Reference material

2.5.1 abbreviation

Write the abbreviations used in this test item in this column .

2.5.2 Definition

The terms used in this project are defined here .

2.5.3 file

The documents and materials cited in this project are listed here .

3． Organization

3.1 Roles and responsibilities

[ Project name ] Roles of test process participants , Responsibilities and skills are as follows :

role	The number of	duty	Skill
project manager		Review and approve the project plan and relevant reports ; Organize and ensure team work ; Control project execution ; Evaluate project performance ; Communicate with relevant personnel .	Familiar with project management knowledge or project management experience , Able to communicate effectively .
Test team leader		Project planning ; Coordinate and implement the activities identified in the project plan ; Identify test environment requirements ; Responsible for designing test cases ; Provide technical support to other personnel .	Familiar with software testing methods and tools , Have a certain ability to lead testers to carry out testing work .
Testers		Perform test activities ; In the project planning stage , Identify project activities and estimate the time required for each activity .	Understand the testing work , The test can be carried out according to the test instructions , And the test results can be simply summarized , Be able to use defect tracking and management system .
Environmental preparation personnel		Provide resource guarantee ; Establish and maintain test environment .	Familiar with the software and hardware involved in the test environment and its configuration , It can quickly eliminate the software and hardware faults in the test process .
Quality assurance personnel		Determine the project quality objectives ; Formulate and implement quality plan ; supervise 、 Guide the implementation process of project activities .	Familiar with software quality assurance and software process improvement concepts , Understand the characteristics and application scenarios of the software under test .

3.2 Testing and training tools

According to the actual situation of the company's project, relevant training can be carried out for testers , Business process training 、 Training on the use of test tools , And list the test tools used in this test

4. Test progress

  The overall progress of this test project is given here .

event	Estimated working days	remarks
Write a test plan
Prepare test plan （ It refers to the planned completion time of each test step ）
Prepare test cases
Perform the test 、 Generate original records
Perform regression tests 、 Generate original records
Prepare test report
Prepare defect report
Submit test documents

5． Testing process

5.1 Test type

List the test types and their descriptions according to the actual project situation of the company .

Test type	Sketch   Statement
unit testing	It mainly checks the correctness of program modules in the process of software development .（ Completed by development ）
Integration testing	It is to assemble all modules into a system or subsystem according to the design requirements on the basis of unit test , Check the correctness of module assembly process and module interface .（ Main background and front-end joint commissioning , And interface testing ）
A functional test	The quality of production software is from user documents 、 Functionality 、 reliability 、 Ease of use 、 efficiency 、 Maintainability 、 Portability and other aspects of quality testing , Help software enterprises find out the problems of products .
The acceptance test	According to the contract terms and system requirements , Overall quality evaluation of software projects , Provide basis for acceptance .
xxx	xxxxx
xxx	xxxxx

                    

5.2 The test method

The test methods to be used in this project are specified here .

[ Example ： The function test mainly adopts manual test method , Black box testing of software products , And the method of black box test .

]

5.3 Test key process areas

The key process areas for completing the test of this project include ：

Ø  Test plan making ;

Ø  Write test cases ;

Ø  Test environment preparation ;

Ø  The test execution ;

Ø  Analysis of test results ;

Ø  Test report .

5.3.1 Test plan making

Prepare test resources , Admission test , The system test , Exit test , And the specific test plan schedule of other tests

5.3.2 Write test cases

How to write test cases is specified here .

[ Example :

Ø  Make test list according to requirements documents, design documents and other relevant documents ;

Ø  Check the coverage of the test case list , After improvement, a detailed test case is formed according to the design method of the test case ;

]

5.3.3 Test environment preparation

It is hereby stipulated that any preparation activities related to the test environment required to ensure the smooth implementation of the test .

[ Example ：

Ø  Prepare the hardware device ;

Ø  Install the software ;

Ø  Configure the network environment ;

Ø  Test data preparation .

]

5.3.4 The test execution

Execute test cases one by one according to test cases , appear bug At the time bug Management tools bug.

5.3.5 Write test report

After each round of testing, write the test report , It is generally reported to the personnel related to the project in the form of e-mail , Report the test situation every week , Describe the test progress , Existing problems and risks , And whether there are special circumstances leading to the change of test plan, etc

5.4 Acceptance criteria

The execution rate of test cases should reach 100%, The passing rate of test cases should reach 80%, all bug Fixed , Reserved bug With the consent of the project leader, it will not be repaired for the time being , Reserved bug It will not affect the normal use of the system software , And issue the exit test report .

6. Related processes

6.1 Defect management

The defect tracking and management tools to be used in this test project are specified here , And outline the graphical report to be submitted when the project is completed .

Example ：

Test the product according to the designed test cases , Defects to be found , Include features 、 efficiency 、 Interface , Record according to the test number in the use case , Ensure the maintenance of various defect records 、 Assign and modify .

Use Zen management tools to track and manage defects , The report submitted at the completion of the project includes the following contents ：

defects ID;

Project name ;

Sample version ;

Test platform ;

operating system ;

Function module name ;

Defect priority ;

Reproducibility ;

submitter ;

Confirmed by ;

Defect problem summary ;

Defect details .

7.  Risks and problems

for example ：

Risks and problems include the following ：

Ø  Whether the development unit completes the scheduled work on time ;

Ø  test plan 、 Testing process 、 The formulation of test schedule is not reasonable 、 standard . In the course of the project , It is found that its operability is not strong ;

Ø  Test whether the required resources are in place . Such as ： Whether there are enough test team personnel , Whether the training of testers is carried out on time , And test whether the skills of the personnel meet the requirements . Test the required soft 、 Whether the test environment such as hardware and operating system is ready ;

Ø  Between testers , And whether there is effective communication between test team personnel and users ;

Ø  Project participants are not familiar with the test tools and systems used , Deviation during use , Affect test efficiency .