Secret script of test case design without leakage -- module test

The last time we talked about the interview, we were asked xxx How to test the function . Today, let's talk about , At work , Give you a specific module or function , How to design use cases .

Never tell me ： Equivalence class , The boundary value , Flow chart and other methods , Because third brother, don't listen , Feel impractical .

So in practice , What is it like ？

At work , In fact, there is no time for you to write function points , And test points .（ These two are in our songqin course , The path of use case design is necessary ）

Because there is no time , Besides , The enterprise unit is looking for you to work , As a software testing engineer , Use cases are outputs , There are no function points and test points , This is auxiliary .

So let's talk about the actual work today , How to skip function points and test points , Design test cases directly . Let's start with a case ：
Here is a login function interface , among ： user name ： Email or mobile number password ： Key in the password ： When the login button forgets the password function encounters such an interface , If you tell me to use the boundary value of equivalence class to verify whether the input box can be input, it's over .

When we go to the test , It must be tested according to the business function or business , Just test one input box , It doesn't make much sense . however , The test case design method of equivalent class boundary value is deep into the bone marrow , I can't say no , It's a little more advanced . Take the above question as an example , Here are two test points , Please judge which is better ？ Test point 1： Verify whether the wrong mobile phone number can be entered into the test point 2： Verify whether the mobile phone number with wrong user name can be logged in. The last two words are different between the two test points ,“ Input ” Is to verify whether this input box can input the wrong mobile phone number ;“ Sign in ” Is to verify whether the wrong mobile phone number can log in .( What kind of wrong mobile phone number , It can be embodied in the steps of the use case ) however ” Sign in ” The two words are about function , Not just the input box , But if there is a problem with the input box, it can also be verified . So we should consider the function when designing use cases , Considering the overall business , We have the above function design test point ：

A little help

Finally, thank everyone who reads my article carefully , Watching the rise and attention of fans all the way , Reciprocity is always necessary , Although it's not very valuable , If you can use it, you can take it !

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 .