Shulou(Shulou.com)06/03 Report--

As software testers, we need to start testing in the requirements phase, because usually before testing, we need to analyze, summarize and review the test requirements to provide reference for the design of the test plan. So what should we do when we receive the test task? The following summary of my suggestions, for reference only, need to be decided according to the actual project situation.

Understand the product

Understand the product deployment environment: the software and hardware environment for deployment, and the differences with the product online environment. Generally speaking, it should be as consistent as possible.

Understand the function of product

Understand the functional purpose

Read the requirements document or design prototype, or verbally ask the product owner what modules the product has. Form a list of product features

Understand the development progress of each functional module, completed / uncompleted. Unfinished reason and completion time

Learn about error-prone modules

Understand known issu

Understand business processes: understand what the business processes of the product are, and construct a business flow chart.

Understand the role of the module, the purpose of the design, in order to meet the requirements of users

Understand the user scenarios of each function and module

Confirm the core functions, main functions, commonly used functions, less commonly used functions, and confirm the application scenarios of important modules (can be used to confirm the focus of testing)

Understand other requirements of the product

Performance requirements

Security requirements

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

Product decomposition

Page link (visit to each page, whether there are 404, 500, etc.)

Function flow (main flow, alternative flow, which can be understood as data flow)

Accuracy of data statistics

Consistency of the same data on different platforms

The unity of the same type of data on the same platform (such as time format, prompt information window-warning class, success class, etc.)

User interface (whether the layout and layout is normal and reasonable)

The process of use case writing and test case writing is also a process of deepening the understanding of the product.

Testing, the testing process can not be plain sailing, will encounter a variety of situations. For example, the system failure caused by some operations may not be taken into account when writing test cases. Therefore, the testing process is not only the best guidance for supplementary use cases, but also a deeper understanding of the product process. Another point to note is that the test process, especially for projects with fast iterations, may not write test cases, but only based on test points. It is difficult to avoid some problems that we are not very sure about the operation steps, including occasional problems, as well as problems with complex paths, often after finding the problem, we can not even remember our own actions before discovering the problem. It is a great headache for testers to encounter this kind of situation. My suggestion is that we can use the screencap tool to record all our test operations during the test. When you encounter a problem that you can't determine the steps, check the recording.

(to be continued) )

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.