当前位置：网站首页>Recommended reading: how can testers get familiar with new businesses quickly?

Recommended reading: how can testers get familiar with new businesses quickly?

2022-07-22 11:23:00 【The elegance of testing】

In the workplace , Learning new business is inevitable , Especially testers , Having good business knowledge is the premise for us to do a good job in quality assurance , No matter in the workplace 「 New people 」 still 「 the elderly 」, The ability to get familiar with the business quickly is indispensable , This is the foundation for us to settle down .

but , Such ability is not very explicit , The author has more than ten years of testing experience , In charge of C End 、B End sum G End business , This article tries to sort out some ways to get familiar with new business quickly , Hope to give you some inspiration .

There are two learning modes

When learning new business , There are usually two modes ：

Teaching style ： teacher / Elder martial brother / Elder martial sister takes you to study , Teach by example and words , Painstakingly add exams ;

Self study type ： Read a pile of learning materials by yourself 、 Test precipitation 、 Business documents , Ask someone again if you have any questions ;

The teaching method is to be taken away by others , Self study is to walk in your own way . From a human point of view , Obviously someone is better , And faster , Tell the key points directly , Avoid the pit , There are teachers and masters who lead them all the way through the pass and kill the generals , Have to upgrade ,！

But in fact , There are not so many experts , Not so free . therefore , In most cases , We are all in the second ： Self study type , Master leads in , Practice in individual , Learn in your own way , Method is particularly important .

Learn to fight monsters and upgrade

When one practices , Learning is similar to fighting monsters and upgrading .

Keep repeating the process of fighting monsters , Is the process of accumulating experience . New monsters emerge in endlessly in business , With new skills , that , To defeat it , You have to improve your skills . Different levels , The strange things you face are different , After promotion , Meet new monsters again , We always have to ask ： What is this ？ How can I defeat it ？ After defeating it , What skills will I acquire ？

This is very similar to the philosophy of security master three questions ： who are you ？ Where to come from ？ Where to ？

If it's monk Tang , He would answer that ： I'm called Sanzang , From the eastern Tang Dynasty . Go to the west to learn sutras .

If it's our 「 new business 」, We should think more ：

who are you ？

What is the new business ？ What is the position in so many products of the company ？ The front desk ？ Zhongtai ？ backstage ？

Who does it depend on ？ Who depends on it ？ Its target users are B End ？C End ？ still G End ？

Its product form is APP？ Applet ？ Website ？H5？PC client ？ official account ？ Or interface ？

Where to come from ？

Why is there this new business ？ What is its positioning ？

What is the value ？ What is the evolution path ？

Where to go? ？

What is the goal of the new business ？

What is the development path ？

What are the phased goals ？

therefore , Learning new business is like fighting strange things and upgrading , Make clear these three business background issues , It will make you more confident about the business details next .

Familiar with the business trilogy

`1. Understand business ： from the outside to the inside`

① Look at the function ： From an intuitive point of view , What are the product functions and business rules presented by the new business ？

For example, e-commerce has greatly promoted , All kinds of preferential goods are directly discounted , Then superimpose the full reduction activities of the platform , Superimpose again 88 Member discounts, etc , You must first understand these product functions and business rules .

② Look at the structure ： From the perspective of business structure , Where is the new business in the whole business segment of the company , What upstream and downstream businesses does it rely on ？

③ Look at the details ： From the details of the product , Each operation step will involve a lot of system interaction .

For example, the preferential services mentioned above , It includes ： Single item discount 、 Business offers 、 Platform offers . During that period , These are actually mixed in use , Each offer will have different application scenarios ; that , Every kind of discount its operation entrance , What interactive systems does it involve , What interface do they interact through , Are to be familiar with and learn .

④ From the perspective of users ： Different users have different demands for the functions of products , It also determines when we conduct business testing , In addition to the accuracy of business , The test focus is also different .

For example, e-commerce has greatly promoted , For the investment attraction system , It is To B The business of , The main appeal is ： System stability 、 Easy to operate , The number of users may be at the level of millions , The main usage scenario of users is through Web End to end operation ;

For trading systems , It is To C The business of , The main appeal is ： System stability 、 High real-time requirement （ Various discounts are updated in time 、 Inventory update, etc ）、 High concurrency , The number of users is at the level of 10 million and 100 million , Users' main devices are mobile phones APP End to end operation ;

After knowing our user population , After basic business function verification , Non functional requirements also need to be validated , For example, how to ensure the reliability of the system with high concurrency , For example, real time during the promotion ( stock 、 Discounts, etc ), How to ensure accuracy ？ Different clients , What compatibility verification is needed ？

⑤ From the perspective of business value ： On business value , In fact, it's about the purpose of our business , What value can it bring , What is its goal ？ It is to supplement the business gap of the company , Expand business territory , Or increase revenue for the company .

When the purpose of a product is to occupy the market quickly , that , We need to iterate quickly , The focus of the test , In terms of efficiency , How to guarantee the quality , Quick release , Some concurrency may be ignored , Or the function of user experience ; If it is a stable business , For example, e-commerce has greatly promoted , After so many years , It is a stable business , How to improve the user experience , Real time , It will become the focus of our test ;

⑥ From the perspective of profit model ： In the capital market , Unprofitable products are easily eliminated .

What is the profit model of the new business we should be familiar with ？ Selling products ？ Selling services ？ Or sell advertisements ？ For testers , Further understand the value of products according to different profit models , Reverse drive us to think about the test focus of the business , This is a very valuable thing ;

`2. See through the business ： System analysis`

After understanding the business , We need to see through the business , Deepen the understanding of the system by dissecting the system .

In the process , We need to understand that ：

The system interaction of the responsible business

How the system interacts with upstream and downstream systems , This is more straightforward , Look at the sequence diagram , Clearly understand the interfaces through which various systems interact , What are the input and output parameters of interaction ？ Understand the system with the purpose of business verification ;

Division of various modules within the system , Which are common modules , What are the business implementation layers ？

From the above two figures, we can see the functions of each module in the application , And some public services and processes , Is the business process we are responsible for going like this , Once you change to a public module or public service , In addition to verifying the current business process , Which related processes still need to be verified ;

How does the data flow ？ How data changes ？

Every piece of data has its meaning , Each field has its specific meaning , Different tables represent different meanings , Different fields also have different business logic . We need to associate the business flow with the data flow behind , In order to better understand every data change , Better lay the foundation for subsequent functional testing , Know which are the key validation fields , Avoid missing function scenarios .

If you are lucky , As soon as you come in , Follow up is a pure new system , From requirements to scheme design to system online , So you're really lucky , You can understand the construction of this system from the beginning , Follow the above way to understand the system and business you will be responsible for ;

If you are in charge of an old business system , Iterating on the old system , that , You can still follow the above 3 To sort out your understanding of business . meanwhile , Look for historical materials , Find senior students to understand the system architecture 、 System module function 、 Data flow, etc , Please ask more 、 ask 、 ask ！

This stage , There's another question I haven't mentioned ： Solutions and means for troubleshooting , We will talk about these next .

3. Optimistic about business ： Hands-on practice

Understanding business 、 After seeing through the business , We need to perform our duties ： see （kān） Good business , Suppose we want to test this business independently , How to test , How to design test cases , How to test , How to verify the accuracy of the function , Encounters an error , How to check ？

Based on the above problems , What we need to do ：

Test case design ： Product based PRD, R & D design scheme and our own understanding of the system 、 Use case design with sequence diagram , Consider basic ： Normal flow 、 Branch flow 、 There are three types of abnormal flow . For the scope of this change, it is necessary to evaluate whether it is necessary to return to the old functions , For some new switches 、 Or cache , Corresponding special verification should be done ;

The test method ： Manual verification or Automated verification ？

Data preparation ： Whether there are ready-made tools or scripts that can quickly generate test data ？ If not , How to create test data ？( The process of making data ？)

The results verify that ： Whether the business presentation meets expectations ,DB Whether the data in meets the expectations ？

Whether non functional verification is required ： Compatibility 、 Security 、 Performance pressure test, etc ;

Troubleshoot problems ： Have a problem , How to check ？（ Locate the root cause , The quickest way to accumulate experience ）

Systematic phenomenon ： Page error reporting 、 The failure of service invocation is an intuitive display , There is also a long process link , It seems that the pages are normal , however DB The data does not meet expectations , Scenarios that will cause errors in the next link ;

Log check ： According to business operation , Look at the background log access , Whether there is error log printing , The log tells you which line is wrong , According to the error prompt in the log , Go to the corresponding branch code to view the code of the corresponding line ;

Data troubleshooting ： Check back according to the data , Based on your understanding of the system , Where will combing involve this DB Change of data , Check back to see the specific code logic , See which branch to go to , Then refer to the corresponding system log , Trace and locate the specific error code line ;

Look at the code ： Whether it's from logs or data , You need to look through the code , occasionally , This line reports mistakes , Not because there is something wrong in this line , But in the middle , Due to the participation problem , Leading to other branches , At this time, we need to study deeply , Where did the mistake begin .

For testers , It is not necessary to completely locate the root cause , But I hope that through such a screening process , Understand the implementation of the system , In the subsequent business changes , You can also understand the scope of the impact of the change , Have your own judgment , Instead of waiting for input from others .

When we can complete the above three steps , Looking back at the business , There may be a sense of Epiphany , There will be a kind of “ So that's it ” The feeling . But we may still be at the beginning stage , The follow-up needs to be repeated continuously 、 Deepen the process of memory to constantly improve our understanding of business .

The construction of business in our mind , It is a process of continuous figuration , Actually , You can also think synchronously ： Is there anything that can be optimized in our original test mode ？ What steps can we take through instrumented means ？ Suppose you need to be a tool to improve efficiency or to improve the project quality of the module you are responsible for , What would you start with , What knowledge reserves do you need to make ... wait , Through continuous in-depth business , Go deep into the system , Think deeply , In order to better stimulate creativity , Bring continuous positive feedback to the work ！

summary

Learning new business , It is a process of continuous accumulation , Only after continuous learning 、 practice 、 Troubleshoot problems , After this repeated process , Will deepen our understanding of business . With business knowledge 、 Improvement of system architecture , It will also feed back our understanding of the business , So as to achieve the change from strange to familiar .

Here's a message ： Better a good memory than a bad pen , Keep a record of , reflection , carding , restructure , There will be surprises ！

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 Key triple connection ！