Friends who have just started to work in testing may have a lot of confusion like me! How to write use cases? Where is the point? What should I do if the project is too late to write use cases? Share your thoughts below, welcome to discuss.
Q: How to get the technical documentation and how to build a test case tree.
Read through the document to clarify the core points of the product (what is the core demand? Where is the advantage compared with competing products? Where is the profit point?).
There must be a test plan/test outline; first grasp the backbone of the product, and distinguish it by module or interface; later complete the test items of each main module.
When decomposing and outputting test items for product requirements/functions, it is necessary to consider both program logic and business scenarios.
Functional use cases and performance use cases, automated. It is easy to distinguish and manage.
The shared modules (data sharing, etc.) in the program need to be marked out for unified planning when writing use cases.
The multiplexing modules in the program are marked out for unified planning. (Code reuse, such as the reports of each interface, many of which are the same code)
The business process is marked out for unified planning. (How many important businesses a product has is determined by the core requirements of the product)
Q: What does a good test case look like?
Coverage--all core requirements are covered; function points must be basically included; scenarios that affect the business should be considered as much as possible. (Unable to quantify, depending on the actual needs of the project)
Easy to execute----one test point and one use case; the execution steps of the use case are clear and the expected results are clear.
Readability--standard wording, consistent font and layout, clear and accurate; ensure that others can easily read and use; (the use case of the company needs to be reviewed, and other tests are used for cross-testing)
Reusability - high reusability; the reusable module can be used with only minor modifications; the utilization rate is high, and the use cases can be used with minor modifications when the requirements are not changed during regression testing.
Automation----Use case writing is considered at the beginning, and it can be changed quickly when automated testing is required (less automation, crossing the river by feeling the stones)
Q: What are the methods of requirement/function decomposition and writing test cases?
Input/Data - Equivalence Class Partitioning
Input/Data - Boundary value selection method
Conditions and Outcomes – Cause and Effect Diagrams
Conditions and Results – Decision Table Method
Scene -------- scene method
Function Follows Data – State Migration Method
A lot of data--orthogonal experiment method
Finally : In order to give back to the die-hard fans, I have compiled a complete software testing video learning tutorial for you. If you need it, you can get it for free【保证100%免费】
Software Testing Interview Documentation
We must study to find a high-paying job. The following interview questions are the latest interview materials from first-tier Internet companies such as Ali, Tencent, and Byte, and some Byte bosses have given authoritative answers. Finish this set The interview materials believe that everyone can find a satisfactory job.
全部资料获取：
