Software Testing Guide

As a software tester, we need to start the intervention test at the requirement stage, because it is usually necessary to analyze and summarize the test requirements before testing, and to provide a reference for the design of the test plan. What should we do when we receive a test mission? The following summarizes my proposal, for reference only, according to the actual project situation to decide.

2. Understanding the product

   1. Understanding the deployment environment of the product: the hardware and software environment of the deployment, As well as the differences in the product line environment. Should generally be as consistent as possible.

   2. Understand the product features

      1. By reading the requirements document or Design prototypes, or verbally tell the product owner what modules the product has. Form the product Feature List

      2. To understand the development progress of each function module, completed/not completed. Unfinished cause vs. finish time

      3. Understanding error-prone Modules
         

   3. Learn about feature purpose

      1. Understand the role of the module, the purpose of the design

      2. Confirm core features, key features (can be used to confirm the test focus)
         

      3. Learn about the application scenarios for important modules

      4. Confirm what is common and what is not commonly used
         

   4. Understand business processes: understand what business processes are in the product, and construct business flowcharts.

   5. Understand other requirements for the product

      1. Performance

      2. Security

      3. Requirements for the environment: operating system, browser (compatibility requirements)
         

4. Product decomposition

   1. User interface

   2. Function
      

6. Use case writing, test case writing process is to deepen the understanding of the product process

8. Test, the test process is not always smooth sailing, will encounter a variety of situations. For example, some operations result in system failure, which may be not considered when writing test cases. Therefore, the test process is the best guide to supplement use cases, but also a deeper understanding of the product process

   (To be Continued ...) ）

Software Testing Guide