Demand phase test work
Author: Jackeichan@gmail.com)
Test cases and testing work is constantly perfect during development. In the early stage of the development process, it can be considered as a demand phase, or there is no design phase of the norms. If there is a relatively clear demand document, you can check the demand document at this stage and start designing test cases after checking.
Here, the inspection of the demand document is mainly two aspects:
1. Check the correctness of the demand document. I think the tester is very familiar with the business involved in the real system, such as a simple financial software, testers need to be familiar with accounting, financial systems.
Do not superstitize the so-called "real needs of users" when checking the demand document. There are two problems here: First, whether the user really describes its needs; the second is whether the demand person can really understand the needs.
There is also whether the needs of the user meet the industry specification. If it does not match, whether it is necessary to confirm that there is a hidden danger: the user may suddenly demand changes in the post-development of the industry, so it takes prior to clear responsibility.
2. Check the accuracy of the demand document. It is mainly considered whether there is a blurred place in the document, and it must be clear for unclear problems. At this time, the testability of the demand is mainly guaranteed, and the need for demand is fully served.
After the requirements are required, you can start designing test cases. I think this stage is due to not starting design work, so it is impossible to start from the interface. The design of this stage test case should be set from the actual business from the actual business. When describing test cases, try to consider how the application is still valid. Of course, the test case implemented at this stage is imperfect and can only cover certain content.
When lacking a demand document, we must play the ability of the test personnel, to take the initiative, not passive waiting. I tried to get familiar with the actual business, try to work through what I can think of.
Finally, in the design phase and the final coding phase, you can continue to add, modify, or delete some test cases, making it more perfect.
Follow-up
This article is also written in 2003 with the article "About Plan Test". In these two years of testing, these methods have proven that these methods are feasible, effective, and of course, but also put forward higher requirements for testers. .
Thoughts, only in sharing and communication can really gain growth, welcome everyone to email, exchange software test related topics, joint progress, together.
Author brief introduction: (black body No. 3. Generally single, all kinds of information is optional, full respect for personal opinion)
