Demand analysis purposes:
First, the user needs into functional requirements: 1) the amount of progress of the test range 2) of the process branches to measure 3) for the needs of the business scenario to measure 4) define the function corresponding to the input, processing and output 5) The implicit type into a clear demand.
Second, a clear test activities of five elements: What are the testing requirements to determine how test, a clear test of time, determined testers determined that the test environment: The test involves the skills, tools and the corresponding background knowledge, you might encounter during the test to risk, and so on. Test requirements as detailed as possible a clear need to do in order to avoid misunderstandings and missed test.
How to conduct needs analysis:
First, confirm the function (business functions, auxiliary functions, data constraints, usability requirements, editing constraints, parameter requirements, permissions requirements, performance constraints):
1, business function: directly related to the actual business functions or user details
2, auxiliary functions: supporting the completion of business functions or features of some details, such as: set the filter conditions
3, data constraints: functional details, mainly for controlling the function is executed, the display range of the data, the relationship between the data and the like
4, usability requirements: details of the function, the product must be provided to facilitate the use of functional operation some details, such as: keyboard shortcuts, etc.
5, edit constraints: the details of the function, while the function is executed, a number of constraints on the input data items, such as: You can only enter numbers, etc.
6, parameter requirements: functional details, when the function execution, depending on the need to set parameters, the details of different treatments
7, permission requirements: functional details, in the course of the functions performed, different treatment depending on the authority, does not include a feature to limit direct authority
8, performance constraints: details of the function, the function is executed, must meet the performance requirements
Second, scene analysis
1, consider the scene of the caller: Consider each service scenario for which is provided by an external module or system calls to identify all callers. Calls premise, constraints must be considered. Each call can be considered as a major business process (in general and there interaction of external business error rate is relatively large, need to focus on)
Consider the system 2 between the interior of each scene: forming an internal business process, the need to analyze the constraints between each scene, the execution condition, a variety of business organizations flowchart
Third, the implicit demand for mining
This requires testing experience engineers: 1) common or prescribed business processes 2) each business process branches traversing 3) clearly defined business processes unusable 4) does not specify but should not be used in business processes 5) other abnormalities or non-compliant operation
These are rough analysis explains how the testing requirements, detailed test requirements can refer to "Software Testing Requirements Analysis" section of this blog. In the course of the preparation of needs analysis throughout the testing program, in the process need to refer to requirements specifications, under normal circumstances at this stage is to write test supervisor. Including testers, test time, test tools and test methods. This is a product of the testing requirements analysis "test plan", how to write test plans, please refer to the following article "How to write a good test plan."