Test Plan (GB856788) 1 introduction testing is required when the basic coding of the project is completed, which plays an important role in troubleshooting and fixing vulnerabilities. 1.1 The main purpose of writing objective tests is to find as many vulnerabilities as possible in the system, design test cases, and test the system. The purpose is to have a general understanding of the testing methods and procedures.
Test Plan (GB856788) 1 introduction testing is required when the basic coding of the project is completed, which plays an important role in troubleshooting and fixing vulnerabilities. 1.1 The main purpose of writing objective tests is to find as many vulnerabilities as possible in the system, design test cases, and test the system. The purpose is to have a general understanding of the testing methods and procedures.
Test Plan (GB8567--88)
1Introduction
Testing is required when the project's basic code is completed, which plays an important role in troubleshooting and fixing vulnerabilities.
1.1Purpose
The main purpose of the test is to find as many vulnerabilities as possible in the system, design test cases, and test the system. The purpose is to have a general control over the testing methods and procedures. This document is intended for testers.
System Testing accounts for 40% to of the total project development process ~ 50%. Basically, the test started during the coding process of the project. Therefore, the quality of the test also affects the function implementation of the system.
1.2Background
Note:
A. Name of the software system to which the test plan belongs: Data Center Charging System
B. the history of the Development Project, which lists the users and the computing centers that run the test of this project. It describes the work that must be done before the execution of this test plan: master the test process and analyze the reliability of the expected results. In addition, testers can run black and white box tests.
1.3Definition
Lists the definitions of specialized terms used in this document and the original phrases of the foreign acronyms.
1.4References
List the reference materials to be used, such:
A. approved plans and tasks or contracts and approvals from higher authorities for this project;
B. Other published documents of the project;
C. Software Engineering Tsinghua University
D. Software Requirement Specification-Xu lingbo
Project development plan-Xu lingbo
Detailed Design Instruction-Xu lingbo
Database Design Manual-Xu lingbo
2Plan
2.1Software Description
Provides a chart that describes the features, inputs, outputs, and other quality indicators of the software to be tested one by one as an outline of the test plan.
Test Item |
Input |
Output |
Quality indicator |
Login |
User name and password |
Feedback |
The information is correctly logged on to the main interface. If the information is incorrect, it is returned to the login interface. |
Query Information |
Basic user information |
User computer records |
The database contains data and the required information is queried. The database does not contain any information and prompts that no information is available. |
Registered User |
Basic new user information |
Prompt information |
Input user information to the database to save |
Modify Information |
Modify user information |
Prompt information |
The modification is successful. |
Combined Query |
Query Conditions |
Filtering Result of the entered information |
The required results can be queried in the output results, and no information is displayed in the DB. |
Checkout |
Date |
All purchase records within the period to be checked out |
Displays all consumption information and generates reports. |
Log out of the user |
Cancel user information |
Prompt information |
The user logs out successfully and changes the user's status in the database. |
2.2Test content
Lists the name identifiers of each test in the assembly test and validation test, the schedule of these tests, and the content and purpose of these tests, such
Module function test
Name identifier |
Schedule |
Test content and purpose |
Query function |
1 day |
Queries the possible query results of all courses to find information that cannot be queried |
Checkout |
1 day |
Check the user's bill to check whether the data is correct, in order to find whether the program algorithm is correct |
Modification function |
1 day |
Modify the data multiple times to find the error data and invalid data. |
This will analyze the test schedule based on it.
2.3Test 1 (identifier)
2.3.1Schedule
Schedules the test, including the date and work of the test, such as familiarization with the environment. Training and preparation of input data ).
Test name |
Start date |
End Date |
Familiar with Environment |
|
|
Training |
|
|
Prepare input data |
|
|
2.3.2Condition
A. device: printer, card flushing machine, PC end with win7sys, 3 computers
B. Software: Office, Grid ++ Report 5.0.
C. Testers: 2
2.3.3Test Materials
List the required materials for this test, such:
A. documents related to this task: test and analysis report and Requirement Analysis Report
B. The program to be tested and its media: the charging system of the IDC
C. charts on the methods and processes for controlling this test: program flowchart
2.3.4Test Training
Describes or references the plan to provide training for the use of the software under test. Specify the content of the training, the trainees, and the personnel involved in the training.
Testers are generally at a higher level than developers. Therefore, testers only need to understand the basic information of the system, read the requirement analysis report, and understand the needs of users.
2.4Test 2 (identifier)
Describes the testing work plan for another and subsequent testing content in a way similar to article 2.3 of this test plan.
3Test Design Description
3.1Test 1 (identifier)
Because the system is mainly composed of several basic functions: Query, modification, and checkout. Therefore, the test plan should be designed for these functions.
3.1.1Control
Manual testing is used to record errors in a unified manner.
3.1.2Input
Test all the data in the database based on the test function.
3.1.3Output
Test Item |
Input |
Output |
Quality indicator |
Login |
User name and password |
Feedback |
The information is correctly logged on to the main interface. If the information is incorrect, it is returned to the login interface. |
Query Information |
Basic user information |
User computer records |
The database contains data and the required information is queried. The database does not contain any information and prompts that no information is available. |
Registered User |
Basic new user information |
Prompt information |
Input user information to the database to save |
Modify Information |
Modify user information |
Prompt information |
The modification is successful. |
Combined Query |
Query Conditions |
Filtering Result of the entered information |
The required results can be queried in the output results, and no information is displayed in the DB. |
Checkout |
Date |
All purchase records within the period to be checked out |
Displays all consumption information and generates reports. |
Log out of the user |
Cancel user information |
Prompt information |
The user logs out successfully and changes the user's status in the database. |
3.1.4Process
Describes the steps and control commands to complete the test, including test preparation, initialization, intermediate step aggregation, and running end mode.
After logging on to the user, verify that the user enters the main interface correctly. Then, the user queries the information as needed and queries the basic information, such as the user name and student ID.
Users with different permissions can perform different operations. For example, an operator can register a general user name, and an administrator can add a new user type.
The Administrator only needs to enter a date period to settle the bill during the period.
3.2Test 2 (identifier)
The design considerations for each of the 2nd items and subsequent tests were described in a manner similar to Article 3. l of this test plan.
4Evaluation criteria
4.1Range
Describes the scope and limitations of the selected test cases.
All the test cases used are known and the data is comprehensive. The basic functions and data of the system can be tested.
The system is small and cannot test highly concurrent test cases.
4.2Data Sorting
Data Sorting uses vb controls and reports to display data. This method is used for data sorting in the query record display and checkout functions. Finally, the data can be exported to excel and summarized and printed reports.
4.3Scale
The evaluation criteria used to determine whether the test work can pass, such as the reasonable output result type, the allowable deviation between the test output result and the expected output, and the maximum number of times the test results can be interrupted or stopped.
1. the user name and student ID have a certain length limit.
2. The input date and time are in a certain format.
3 ,...