Time: 2004/5/15 Author: Robert Email: zsc771120@yahoo.com.cn Keywords: test test Bug
Objective: To improve friends' test level
A week, the bug I tested is more, telling me that I have a test.
in principle:
1. The test data is abundant, you can't enter the correct data, test OK, you will do it more sensitive data.
Example: System management path, you can enter "Chinese" "English" "English" "correct path" "C: ///" These relatively sensitive text. We can see what the result will look like.
2. Don't pay attention.
Example: Select the member's advanced settings, will see 1-16 of the extension line list, we choose the correct extension, this should not appear 1-4, this error can be told by the user: "Experience 1-4 is outside How can I allocate it to the user? "I think it is a problem with the program. If our extension option is 5-16, there will be no user to fill in 1-4 problem. So this can be counted for BUG, you can also If you are concerned, you can't compromise, this is bug.
For example: the membership mailbox has a short message transmission problem, and the handbox will have a short message to send a problem in the assistant manager. This is two bugs. Don't think the bug, the record is good.
3. Don't be afraid.
The test is for an error, the more the error, the more the test is successful. If the user uses our system, we are in the top eight, then we must not be peaceful, always worry that there is a mistake. I think: Let customers go to the customer, it is better Let's take a look at it and take the operation we can think of, and you can do it again until we think users will operate, even if there is an error, we know what the mistake is.
4. There is no authority in the test.
Example: System mailbox changing path, no one can operate, if we test must be actions. What are you doing? There is an error can be modified. If you have a mistake, it is a big thing on the face. Where you can operate, we have Go to the operation and do more unconventional operations.
5. Do not test for an error.
All of our testing data is all entered. There is no problem in the system. We feel that there is a problem, desperately testing this function, must find a mistake. This is not necessary, basically testing a data is not wrong, if there is anything Errors, also use errors, there is also an error, record.
6. Don't be afraid of trouble and want to be of course.
There is a SMS send in the membership mailbox. There is also a SMS send in the Assistant Manage mailbox. Don't judge another OK because of an OK. It must guarantee that it is the hard truth.
step:
1. Look at the test form big item, understand what functionality is now tested.
2. Exploide the test form, do this function yourself. Don't wait for it, you will lose everything. Let's go away, you want to do it, how to do it, see if the function is complete, there is a record, you can't It is said that there is a mistake, and this error cannot be reproduced without recording.
3. Look at the test form small item, fill in the test form. There is no test for a small item re-test. Here, pay attention to the results must be in line with the test results. A little bit does not meet, record, it is bug.
This is my test experience, welcome to exchange experience.
Let's cheer, let our system are more robust.
