Software Test Plan-Example

 

 

Software testing plan

 

 

 

 

 

 

 

Document____________Date:___/___/___

Development/Test Manager:____________Date:___/___/___

Product Manager:____________Date:___/___/___

 

 

 

 

 

 

 

 

 

 

 

 

 

 

XxSoftware testing plan

I.Overview

1.1Purpose

The purpose of this plan is to ensure that the corrugated logistics system can meet the functions described in "xxxx" and check whether the system is running stably.

1.2References

A.《xx ((.pptx

B .《xxsystem detailed design .docx

1.3Background

Corrugated Paper is gradually becoming more refined, repeatable, white-faced, low weight, and miniaturization. In the face of the trend that some micro-Corrugated Boxes have begun to compete for the market with traditional Corrugated Boxes, the rapid development of foreign micro-Corrugated Boxes and the constant expansion of China's market needs should change the current situation of micro-corrugated board technology and equipment in China as soon as possible, and increase the development of micro-Corrugated Boxes, actively promote the development of micro Corrugated Boxes in China.

In order to facilitate management, improve the efficiency of production management, save manpower and material resources, and develop the corrugated paper logistics system software, which consists of two main modules: raw paper warehouse management and cardboard logistics management.

II.Conventions

2.1Purpose and task of testing

The purpose of this test is to test the entire system and verify the basic availability, functional integrity, and data accuracy of the software.

The task of this test is:

A. Check whether the functions completed by the software are consistent with those described above in comparison with the Property Management System Requirement Analysis Statement of the property management system System Analysis Statement;

B. Can the data service be completed correctly;

C. Whether the entire system can run stably;

D. Whether other installation instruction files such as help are correctly expressed.

2.2Personnel and equipment

A. personnel:

Tested :**

Programmers :***

B. device: Server IP Address: 192.168.62.39

One printer

2.3Test delivery requirements

The tests submitted by property management system developers are carried out as follows:

Procedure	Action	Owner	Related documents or records	Requirements
1	Packaging and compilation	***	None	Confirm Testability
2	Receive Test	**	User requirement specification System Design Specification	Confirm start test
3	Start testing	**	Bug list and summary	Test Summary write personal content

2.4Numbering rules:

A. number in the test case, Module name + Interface Name + number

For example, fcgl-rzgl-001

B. Naming rules for test case file, Module name + Test Case

Example: Business Server Management tenant management case

The bug numbers in the test bug list record also follow the numbering rules in the test case.

2.5Test schedule and progress

The schedule is as follows:

Test phase	Test task	Workload Estimation	Personnel allocation	Start Time and End Time
Stage 1 Function Testing	1. Real Estate Management 2. Business Server Management 3. Fee Management 4. Customer Service Management 5. device management 6. Security firefighting 7. decoration Management 8. Environment Management 9. Personnel Management 10. System Maintenance Whether the function can be correctly implemented and whether there are operation errors.	4th	**	041126-041130
Stage 2 System Test	1. Complete the Combined testing of all modules 2. Make sure that all business flows and data are correct.	3 days	**	041201-041203
Stage 3 Performance Testing	Load suppression tests are performed alternately during multi-user access.	1 day	**	041205
Stage 4 Installation manual Help File testing and Installation and detachment Test	1. Compare the installation manual and user help manual with software operations 2. Test the Installation File	2 and 1	**	041206-041208
Stage 6 Compatibility Test	Running status of software on various software platforms	1 day	**	041209

Iii. Test types and test standards

3.1Function test phase

A. function test: test whether the functions of each module and window are accurate, whether the data is correct, and whether the operations are simple and convenient.

B. function keys and interface tests: whether the function keys are described accurately and easy to operate. Whether the interface design is concise meets user requirements.

C. Data item test: 1) whether the correct data can be displayed according to the expected answer;

2) identify incorrect input data and provide correct information;

3.2System test phase

A. Business Process Test: Check whether the business processes completed by the system are correct according to the Business Process in the system analysis manual.

B. Data Flow Test: whether the data involved in the system flows according to the correct business process and whether the data results reflected by each stage are correct.

3.3Performance testing stage

The customer simulated a multi-user test. The stress test has a principle. And 80% of business volume input within 20% of the time.

3.4Installation manual help file test and installation/uninstallation test phase

A. Test the Help File: 1) whether the help document accurately describes how to use various features

2) is the example accurate?

3) are terms, menu descriptions, and system responses consistent with the actual program?

4) Can the Guide be easily located in the document?

5) is the document easily used to eliminate errors?

B. Installation and detachment test phase:

1) automatic installation or manual installation, test various installation combinations, and verify various groups

The final goal is that all combinations can be installed successfully.

2) After the installation and exit, confirm that the application can be correctly started and run.

3) The uninstall test and installation test are equally important. If the system provides an automatic uninstall tool, you must check whether the system deletes all the files after uninstallation, whether the registration information in the Registry is also deleted.

4) is the installation time reasonable;

5) for an application system in the client server mode, you can first install the client and then the server to test whether the problem may occur.

3.5Compatibility test phase

Verify the running status of the software under several common operating systems, and check whether the software and other software are running correctly in parallel.

3.6Key Testing

"Fee charged" in fee management"

3.7Test Design

See the test case design manual.

4. Test submissions

Submitted after the test is completed:

A. Test Plan

B. Test Cases

C. Test the bug list

 

 

Software Test Plan-Example