How to write high level test cases? This is a question that testers often ask.
As the sorghum is not a day, it is necessary to have a good test case requires the accumulation of experience and knowledge.
For the current software enterprise environment, individuals have summed up the following writing cases:
Enterprise environment:
Number of people: 100
Product Type: Enterprise Informatization, Office Automation
Number of testers: 5
Development environment:
Have a development process and standard (real run is not very good, the reason is much, there are also company officials, etc.)
Have testing process and standards (not very good in the development process and standardization, it is not very good)
Test case:
Originally, the reference software requirements instructions are written, and the input portions in the use case mainly include verification data in UI; data of text box checks data; software function verification data
Disadvantages: The writing of general use cases can be carried out after review, but the company's current situation, one is frequent demand for users, and the second is that the demand written by the developers is not detailed, and the logical relationship cannot be fully reflected in the document.
At present, the use case is mainly divided into the following parts: 1, text box entry detection rule 2, easy to use sexual detection rules 3, rationality detection rules 4, help document detection rules 5, system resource detection rules 6, function test (with data flow The picture reflects the logical relationship in the software, especially software, more complex business knowledge, what operations are made in the past describe, after doing operation, time, labor efficiency)
Advantages: The entire document is concentrated, clear, and will not confuse the host
