Test report on the idc Charging System

 

1. Project Information

Project name: Data room Charging System

Project start time: January 1, August 1

Project acceptance date: January 1, August 18

2 Project Overview

3 Acceptance Test Environment

Hardware 3.1

Computer, server, network, card reader

Software 3.2

Operating System and test program

3.3 documentation

3.4 personnel

Jiang qianlan, Cao Jianxin, Wang boxian, Zhao Jie, Tang Changhai

4. product acceptance results

Developers	Product Name	Acceptance result	Acceptance person	Acceptance time
Jiang qianlan	Data room Charging System		3.4	August 18

5 acceptance Summary

5.1 Aesthetic Problems

5.1.1 the size of the form can be adjusted at will, but the position of the control inside is fixed, which leads to a particularly poor aesthetics of the entire form when the size of the form is different.

5.1.2 the size of the same control is inconsistent, or the size is not large. The size is not small and does not comply with the design requirements.

5.1.3 The text font displayed in the control is too small.

5.2 robustness

5.2.1 the size and format entered in the text box do not match the database, leading to Data Reading failures and errors.

5.2.2 some text boxes do not need to be input but only need to be output locked.

5.2.3 deleting a record does not determine whether the record exists and causes an error.

5.2.4 some records that need to be updated at any time are not updated at any time, such as the number of persons on the computer and the records on the computer Status view.

5.3 portability Problems

5.3.1 for example, some machines run well, but the other machine cannot run. xianer started with this problem and found that the reference level of a part was too high, therefore, some machines cannot be used.

5.3.2 report packaging problem. Because a third-party control is added this time, the packaging is different from the previous one. For the first time, a component is not packaged, so the report on the data center on the fifth floor is always unavailable.

6. Suggestions

6.1 you should have a detailed understanding of the entire program before, and it is best to write a document.

6.2 The time must be properly arranged. Do not make yourself uncomfortable if you are loose or tight.

6.3 it is best to write data according to specifications when writing data, so that it will not be annoying at any time.