Test Analysis Report
1 Introduction
1.1 The purpose of writing
The Test analysis report is the process of analyzing and summarizing the function problem of test data on the basis of testing, and the test process is an indispensable part of software development. It plays an important role in the upgrading of software functions. Moreover, for the future developer reading source program, according to test data and results analysis software functions and limitations laid a good foundation. Developing software for developers saves a lot of time and effort.
The intended audience for this document is software developers.
1.2 Background
A, to be developed software name: Computer room charge system
B. Project Author: Professor Mi Nue-jiang
Developer: Zhou Jialin
User: All teachers and students of Langfang Normal University
The computing center or computer network that implements the software: Campus LAN of Langfang Normal University
C, the basic relationship between the software system and other institutions: from the information technology accelerated of Langfang Normal University to do technical support.
1.3 Definitions1.4 References
"Software Engineering" Zhang Haifan People's post and telecommunications press
"The Classic of SQL Getting Started" Offujiang translation
"VB Program design Textbook"
Examples of database Redbook
"Chen Wei VB6.0 video"
2 Test Summary
Lists the identifiers of each test and the test contents as well as the test results in tabular form, and indicates the difference between actual and planned, and seeks the reason.
3 Test Results and findings
3.1 Basic information Test (BASICDATA_INFO)
The actual results obtained in this test are exactly the same as the requirements, which proves that the program of the module is not abnormal, and the system is synchronized with the database data.
3.2 User Information Test (user_info)
The actual results obtained in this test are exactly the same as the requirements, which proves that the program of the module is not abnormal, and the system is synchronized with the database data.
3.3 Checkout (Check)
The actual results obtained in this test are exactly the same as the requirements, which proves that the program of the module is not abnormal, and the system is synchronized with the database data.
4 Conclusion on the function of software
4.1 Basic Data Settings (Basicdata_info)4.1.1 Capacity
Ensure the system put into test run, the most basic data set to and database accurate docking.
4.2.2 Restrictions
Basic data settings are not strictly limited, as long as they are realistic.
4.2 User Information settings (user_info)4.2.1 Capacity
This part of the main functions include user registration, recharge, on the machine, card, such as a series of functions, after testing, the system can correctly complete the student registration, recharge, return card services.
4.2.2 Restrictions
Because this part of the function is more extensive, the program section is responsible for the input data requirements are more stringent, so this part of the test is the main limitation of the students throughout the use of the process of grasping and control, such as to test the machine, recharge and return card function, first of all to ensure that the corresponding card number has been registered, to be able to have
4.3 checkout Setup (Check)4.3.1 function
This section is mainly for the function test of the administrator, the administrator to the operator to checkout operations.
4.3.2 Restrictions
The checkout process has a mouse complete and no keyboard type exists.
5 Analysis Summary5.1 abilities
State the capabilities of the software that has been tested and verified. If the tests are performed to validate the implementation of one or more specific performance requirements, you should provide a comparison between the test results and requirements in this area, and determine the impact of the possible differences between the test environment and the actual operating environment on the ability test.
After testing, the software has the functions required in the test plan, meets the required competency standards, and meets the requirements of software performance.
5.2 Defects and limitations
Although most of the testing has achieved the expected requirements of the system, there are still a small number of defects.
A. In the checkout module, the output of the weekly checkout order is sometimes not arranged in chronological order, which is inconvenient for the administrator to manage the information.
B. In the case of operator work records, the system usually stores the duty record after the operator has logged off, and if the operator is not logged off normally due to a power outage or a system failure, there is no record of the operator's work.
C. Restrictions: The system can only operate properly if the server is connected.
5.3 Recommendations
Based on the problems exposed in the test analysis report, find out the source code for optimization.
A. Modification method: program code debugging
B. Urgency: Important
C. Expected workload: Improved work guaranteed to be completed within 3 days
D. Change in charge: Zhou Jialin
5.4 Reviews
After testing, the software development is basically in line with the needs of users, but some of the details still need to be improved, after optimization can be delivered to users.
6 test resource consumption
Personnel consumption: 6 Test personnel required to complete the test work.
Machine consumption: About 6 days
Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.
Computer room charge system-Test analysis report