当前位置：网站首页>Technology sharing | do you understand the requirements of the tested project?

Technology sharing | do you understand the requirements of the tested project?

2022-06-23 14:09:00 【Software testing】

Insert picture description here
Requirements analysis is the first step to start testing , The product will first produce a requirements document , Then we will organize demand publicity , Analyze whether there are problems in the demand in the demand publicity , Then after the lecture , Analyze the test points through the requirements document and estimate the schedule . So understanding the requirements is very important .

The requirements document

After the product manager completes the user demand survey , A requirement document will be output according to the user's requirements , The functions required by users and the effect of function realization will be described in detail in the document . After document generation , The product manager will hold a requirements briefing with the development and testing , Explain the contents of the requirements , And the possible problems in the requirements will be discussed .

Requirements review

In the process of demand publicity , In fact, the requirements themselves need to be reviewed . Requirements review can be considered from the following perspectives .

Business scenario perspective

From the user's point of view , Consider the various situations that users will encounter , In contrast, whether the corresponding description can be found in the requirements of various situations , That is, user stories

It should be possible to build simple flow charts based on user stories , Constraints between various paths , Whether there is a clear and reasonable definition of execution conditions , Business process diagram

Function point angle

Whether the data constraints are comprehensive 、 reasonable

There are branches of logic 、 Describe whether to overwrite all paths

Multi state process , Whether the state flow description is reasonable and complete

Is the permission description clear

During the review , It can be considered from these angles , Check whether the requirements written by the product are perfect . If there are imperfections in the demand , Ask questions and discuss them with product development . The ultimate goal is to make the demand more reasonable and complete .

Demand analysis

After the product manager finally improves the requirements , You can analyze the requirements document in detail . Requirements analysis is simply to simplify the non intuitive requirements documents into intuitive requirements .

Requirements analysis steps

Define the scope of the test ： Determine the boundary of test activities , Because many modules are related , During document analysis , It depends on whether the coupling between the functions to be added and the previous functions is high , Do you need to test the associated functional modules .

Define function points ： List the function points in the requirements document .

Clear business process ： Sort out according to the business flow chart .

Clear output results ： Easy to verify .

Analyze the abnormal process ： Improve the fault tolerance of the system .

Estimate the time and resources required for testing ： Prepare for the preparation of test plan .

In order to improve the ability of demand analysis , We need to deeply understand the requirements .

How to improve the ability to understand requirements

Familiar with the business , Understand the system . Any system has a large business background , As long as you are familiar with business knowledge, you can use the system more effectively . Any system in use , There is a familiar process , The more familiar with the system , The easier it is to find system problems and business problems .

Analyze from the perspective of users with an objective way of thinking . On the basis of meeting customer requirements , From the perspective of business or existing system implementation , Give some design suggestions to requirements and developers .

Good at summarizing , Willing to share . Share the common misunderstandings of use case design and some good requirements analysis examples and requirements analysis habits with the people around you , This can bring together the strengths of everyone , Continuously improve the ability of demand analysis .

The technology industry should continue to learn , Don't fight alone in your study , It's best to keep warm , Achieve each other and grow together , The effect of mass effect is very powerful , Let's learn together , Punch in together , Will be more motivated to learn , And you can stick to it . You can join our testing technology exchange group ：914172719（ There are various software testing resources and technical discussions ）

Here's a message for you , Mutual encouragement ： When our abilities are insufficient , The first thing to do is internal practice ！ When we are strong enough , You can look outside ！

Insert picture description here

Finally, we also prepared a supporting learning resource for you , You can scan the QR code below via wechat , Get one for free 216 Page software testing engineer interview guide document information . And the corresponding video learning tutorial is free to share ！, The information includes basic knowledge 、Linux necessary 、Shell、 The principles of the Internet 、Mysql database 、 Special topic of bag capturing tools 、 Interface testing tool 、 Test advanced -Python Programming 、Web automated testing 、APP automated testing 、 Interface automation testing 、 Testing advanced continuous integration 、 Test architecture development test framework 、 Performance testing 、 Safety test, etc. .

Friends who like software testing , If my blog helps you 、 If you like my blog content , please “ give the thumbs-up ” “ Comment on ” “ Collection ” One button, three links ！