1. Test requirements analysis
It is mainly analyzed from the following aspects:
1: Definition of requirements.
2: Test Requirements Analysis Process 3: Test Requirements Analysis Process Purpose: Requirements are to solve what to do, not how to do it.
Second, the process of software testing:
1. Test requirements analysis stage: read the requirements, understand the requirements, mainly to learn the business, analyze the requirements points, and participate in the requirements review meeting. 2. Test planning stage: the main task is to write the test plan, refer to the software requirements specification, the overall project plan, including the test scope (from the requirements document), scheduling, the allocation of manpower and material resources, and the formulation of the overall test strategy. There is a development of risk assessment and mitigation measures.
3. Test design stage: mainly to write test cases, will refer to the requirements document (prototype diagram), outline design, detailed design and other documents, and will be reviewed after the use case is written. 4. Test execution stage: set up the environment, execute the smoke test (**test) - and then enter the formal test, bug management until the end of the test.
5. Test and evaluation stage: issue a test report to confirm whether it can be launched.
Definition of requirements: (1) Product requirements: the conceptualization stage enters the drawing stage. Contains the features and performance metrics of the product.
2) Customer needs: The relevant requirements of the demanders are called customer needs.
3) Requirements specification: test requirements: requirements analysis is the process of mastering the system being tested, and generally the test and developers have to conduct requirements analysis, and the requirements analysis done by the tester is called test requirements analysis.
Definition of Test Requirements Analysis: Human Words: An Analysis of One Objective of the Testing Process:
1) What are the test requirements:
Solve the problem of what to test - the test objective (test object) specifies what requirements test in the test object - what each target is to test.
2) Test Requirements Analysis Method:
It is usually based on software development requirements, a foundation (requirements document), a detailed decomposition, and a method (layer by layer decomposition).
3) Test Requirements Analysis Scope:
All cover defined business processes - functional and non-functional aspects of the business process - functional (non-functional: performance, security, compatibility).
3. Characteristics of test requirements.
4. Tools for testing requirements: The tools and templates for testing requirements will be different for each company
It is used to refine and decompose test points, and is easy to edit and widely used.
Fifth, the process of demand analysis: to ensure that the test requirements cover the requirements as much as possible.
Test Requirements Analysis Performers.
Process: Requirements collection - > requirements analysis - > requirements review.
Output: 1Test the requirements document.
3.Process documentation that proves that the test requirements document is correct.
4.Audit results.
Original Test Requirements Table: Test Requirements Tracking Matrix Review Conclusions.