Test the data room Charging System

I went to Cui chenglong last night to help test the fee system of the new data room. Because of my first experience, this is much lower than the last error. But I still found some problems.

1. In the basic information maintenance function of students, click the datagridview column title to sort the information, resulting in asymmetric row information.
Solution: Search for msdn and find the datagridview. In its event description, click an event in the column title to handle information asymmetry in this event.
Problem.

2. Rational judgment of basic data. For example, the minimum recharge amount cannot be greater than the maximum Recharge Amount, not less than 0, and the preparation time cannot be greater than the unit charge time.
Solution: Based on basic knowledge, add judgment to the corresponding method.

3. When querying student information, a judgment cannot be found; otherwise, an error occurs in obtaining the text box for updating information.
Solution: Add judgment.

4. User information management: the data in the database is directly updated through the datagridview, and the user level lacks legality judgment. As a result, the user level is changed and the logon fails. If the data of other columns is invalid, the system default error message is displayed, comparing the users.
Solution: try to change this column to a drop-down box. You can only select this column. You are not allowed to enter the column. If it fails, set this column to read-only for the moment. Rewrite the dataerror event and write your own data with an invalid message.

5. Empty rows at the end of the datagridview table. If empty rows are selected, the point is forced to drop.
Solution: Set the attribute of the datagridview to No.

6. Test on XP and win7 and find that the date format is not compatible. Similarly, after "/" format is used, the separator for saving a database is "-", and the separator for storing a database is "/".
Solution: Use "-" Format

7. During packaging, the. NET environment is not entered, causing a prompt to download. NET Framework installation during installation, which is a waste of time.
Solution: repackage and add the local environment to the deployment file-properties-system prerequisites.

Some details have been resolved:
8. Refresh the report because you can obtain the latest checkout information.
9. font of the checkout form
10. The query is on the machine. The combo box control does not judge the null value.
11. The DTP date control can set the minimum and maximum values to prevent the selection of dates from being too outrageous.
12. Check whether the size of some controls is neat and the font is inappropriate.
13. avoid entering spaces in the password

This time I used object-oriented programming, basically there were no major logical errors, because the debugging was easier than the previous design, and the entire architecture was there and I was very familiar with it, so there are very few cases of instant transmission and full body movement. There are still many issues in details. I think this is the quality problem. For example, judging the legitimacy of data input is the most basic quality. Adding comments is also a manifestation of quality. If you have a good habit, you can avoid many details.