Software testing experience sharing and 8 suggestions

This article mainly introduces the sharing of software testing experience and 8 suggestions. It has certain reference value. Now it is shared with everyone. Friends in need can refer to it.

Many people think that a software is written Test cases are not important. This idea is wrong. The most basic test cases are not available. It is equivalent to testing aimlessly and will definitely not achieve the effect. Here I will tell you how to write test cases. If something is wrong, you can send me a message so that I can learn from it.

Test cases should be written before the project starts. For small projects, you can just use an Excel spreadsheet. For large projects, you can use online tools, such as bugfree and ZenTao.

I would like to give you some suggestions for writing:

1. You can click the button on the page to write. For example, the login page, how to enter the login page is considered a test case. Return to the previous page to calculate a test case. Click to log in. In several cases, there will be several test cases. The more detailed the better.

2, You can write it in page effect. For example, on the homepage, if there are typos in the text, it will be counted as one, if the category is added, modified or deleted, and if the display is normal, it will be counted as one.

3. If it is an order, the amount needs to be tested by making an error. For example, an error is reported after the order payment is successful. The user's money has been paid, but the software has not received it. Is there any follow-up solution?

4. Bug levels can be divided into: S fatal error, which seriously affects the use or the interface cannot be opened and the requirements are not realized. A data error. B responded too slowly (exceeded the response time). C makes suggestions for modifications that are unreasonable.

5. The mobile phone or computer version, system version, tester, and test time must be clearly listed.

6. If S and A exist, they cannot go online.

7, Bug graphic statistics for easy viewing by leaders.

8. The person responsible for the bug must ensure that the same problem does not occur three times for a bug. A strict company does not allow the same problem to occur twice.

The above is the entire content of this article. I hope it will be helpful to everyone’s study. For more related content, please pay attention to the PHP Chinese website!