With an annual salary of 50W, Alibaba P8 will come out in person to teach you how to advance from testing

How new testers can quickly determine software problems , Test how people who have been working for some time grow ？ Nonsense , Direct delivery of dry goods ！

How to quickly find out the program / Software problems

01、 Test the changed part first （ Such as new demand 、 A modified bug Code for ）, Retest the unchanged part .

because ： Modifications and updates mean new risks .

02、 Test the core first （ Such as key functions 、 Core requirements ）, Then test the auxiliary function .

because ： In a limited time , After testing the key and common functions , It means testing the basic functions of the product .

03、 Test the function first , Then test the performance .

because ： Only when the function is normal , Testing performance makes more sense , Otherwise, after the function is changed , Previous performance test reports become useless .

04、 Test common scenarios first , Then test the rare scene .

because ： In a limited time , Completing the common scenario test can cover the user's use scenario as much as possible , Avoid basic mistakes .

05、 First test the problems that have a great impact , Then test the problems with small impact .

because ： A problem with a large impact causes more damage than a problem with a small impact .

How to provide a convincing test report

01、 Collect and provide test evaluation evidence , Such as test environment 、 Method of recurrence 、 Recurrence frequency 、 Screenshot of fault phenomenon / Video recording, etc .

because ： Sufficient evidence and information can reduce the communication cost between testers and developers , It can help developers locate fault codes quickly .

02、 Try to use logical expressions , Such as given……when……then, Statement known xx Under the condition of , Conduct xx operation , produce xx result .

because ： While sorting out the logic, the tester , It can deepen the determination of fault inducement , And a logical and clear expression allows developers to quickly understand the causes and consequences .

03、 Effectively expand inferences , Such as the impact of the current fault , Other modules or functions that may be affected .

because ： Some faults （ Such as interface failure ） May affect other modules , When analyzing the impact of current faults , Inferring the spread to other modules can find hidden spread faults in advance .

How testers think

01、 Technical thinking , Such as understanding the program / Software internal structure 、 Data flow process 、 State transition and so on .

because ： Only understand the internal operation of the software , For more in-depth testing , Dig deep faults .

02、 Creative thinking , Such as making effective inferences about the observed phenomena , Look for possible problems , Or use tools / Test method to imagine , Find more effective tools .

because ： Creative thinking , Expansive inferences are more “ Strange soldiers win ”, Improve test efficiency .

03、 Think critically , If not “ parrot ”, When a phenomenon that may be a fault is observed , Don't give up because of the negation of developers , To stick to “ Look for the truth ”, Even if it turns out that it's not a fault .

because ： Developers may also be limited to some scenarios , Misjudgment , stay “ Look for the truth ” In the process of , Can deepen the understanding of the program / Understanding of software , Collect enough evidence to complete the judgment .

04、 Practical thinking , It's on paper , You need to know that at this time, you should practice . Only thinking in practice can have results , Otherwise, it will end up on paper .

because ： Even comprehensive thinking and effective inference will inevitably be omitted , Only in practice , Constantly improve and optimize , To put the thinking plan 、 The method is organically combined with the actual situation .

How to explore in practice

01、 Explore forward , Explore the unknown from the known .

Such as ： An interface configuration page , Click on “ The next item ” try .

02、 Explore backwards , Return to the previous state from the current state .

Such as ： An interface configuration page , Click on “ Last item ” try .

03、 Horizontal exploration , Jump out of the current state , Switch to another state .

Such as ： An interface configuration page , Configuration not completed , Refresh the page and try .

How to quickly generate exploratory testing ideas

01、 Test program boundary , The commonly used boundary value test method .

Such as ： An input window restricts input 1-100, try 1 and 100 Input value test for .

02、 Test all error messages , Exception code handling .

Such as ： Program operation overflow causes memory increase , Overflow exceptions occur frequently, which may lead to memory overflow .

03、 Test non default configuration .

Such as ： The software installation will provide the default option configuration , Try a non default configuration .

04、 Test limit test .

Such as ： In case of hardware resource alarm , Test the operation of the program .

Many people say that testing requires experience , You bet , Experienced guidance can help testers better test .“ Test experience ” Let's stop here for the first part ~

The house needs to be built layer by layer , Knowledge needs to be learned at one point one . We should lay a good foundation in the process of learning , More hands-on practice , Don't talk much , The last dry goods here ！ I stayed up late to sort out the stages ( function 、 Interface 、 automation 、 performance 、 Test open ) Skills learning materials + Practical explanation , Very suitable for studying in private , It's much more efficient than self-study , Share with you .

Get off w/x/g/z/h： Software testing tips dao

Typing is not easy , If this article is helpful to you , Click a like, collect a hide and pay attention , Give the author an encouragement . It's also convenient for you to find it quickly next time .