Login, registration and forgotten password test points of mobile APP function test

For an APP, the three functions of logging in, registering and forgetting the password are the most important for both the user and the APP itself. Therefore, special attention should be paid to these three functions when doing APP function testing . Login Login module It is relatively simple, there is only one interface, and the focus is on the testing of error messages under abnormal conditions. The main ideas are: type, length, null, default value, business constraints, and repetition. Take our company's app as an example, the login is divided into account and password. The account is a mobile phone number, so the requirements are: 11 digits in length, and the default is empty. Main tests: 1. Only numbers can be entered, and letters, special characters and spaces cannot be entered. 2. The length is limited to 11 digits, and an error will be reported if less than 11 digits: Please enter the correct mobile phone number. 3. Whether there is a corresponding prompt when entering a mobile phone number that does not exist. 4. Enter the unregistered mobile phone number and see if there is a corresponding prompt. The password is a combination of numbers and letters, the requirements are: 6-12 digits and letters, the default is empty. Because it is a login, as long as it is divided into two cases, right and wrong, the login is successful directly. If it is wrong, you can test it in the following cases: 1. Enter the password at will, of course, it is inconsistent with the correct password, and see if an error is reported. 2. Enter the wrong password several times to see if there is a prompt before the password is locked. 3. Enter the wrong password for a specified number of times to see if the account is locked. 4. After the account is locked, enter the correct password to see if you can log in successfully. Registration There are multiple interface jumps for registration, but in summary, there are two steps, one is to fill in the account password, and the other is to fill in the verification code. I call them the registration interface and the verification code interface respectively. The registration interface is mainly to fill in the account and password. The idea is similar to the test of the login interface, but also different

























Or the account is a mobile phone number, so the requirement is: 11 digits in length, the default is empty. Main test:

1. Whether there is a prompt message in the account input box: Please enter the mobile phone number. (The prompt information can let the user know the filling rules)
2. Only numbers can be entered, and letters, special characters and spaces cannot be entered.
3. The length is limited to 11 digits, and an error will be reported if less than 11 digits: Please enter the correct mobile phone number.
4. Whether there is a corresponding prompt when entering a mobile phone number that does not exist.
5. Enter the registered mobile phone number and see if there is a corresponding prompt.

The password is a combination of numbers and letters, the requirements are: 6-12 digits and letters, the default is empty.

1. Whether there is a prompt message in the account input box: 6-12 alphanumeric combination
2. Enter special characters and spaces to see if it can be entered or whether an error is reported.
3. Enter pure numbers or pure letters to see if there is an error message
4. If the input is empty, see if there is a corresponding prompt
5. Enter less than 6 digits, 6 digits, 6-12 digits, 12 digits, greater than 12 digits, check the corresponding (Boundary value method, based on experience, the boundary value cannot be ignored, there is a possibility of flashback), the

check code interface will be relatively simple. Mainly check whether the countdown frequency is correct, whether there is a corresponding prompt when the check code is wrong, and whether there is a corresponding prompt when the check code is sent frequently.


Forgot password

Forgot password is mainly divided into three parts, input account, get verification code, reset password.

1. Whether there is a corresponding prompt when inputting less than 11 digits or an incorrect account
2. Whether the jump can be successful when inputting an unregistered account
3. Whether the jumping is successful when the correct account is
input 4. Whether letters, special characters, and blanks can be input

Get verification code. Test the verification code test when registering as above.

reset Password. Test the test of the password when registering as above.

When you need to pay attention, after the modification is completed:

1. Use the old password to log in to see if the login is successful.
2. Use the new password to log in and see if the login is successful.
3. In the process of resetting the password, check whether the account can be changed, and the function of modifying the password of other accounts.

This is probably the content. The test points that need attention as a whole are:

1. Jump between pages and use of the return function.
2. After the sub-module test is completed, go through the general process again.
3. When the requirements are unclear, check the handling of similar situations of similar software.


Every time I do an APP test , I usually pay attention to this part of the test and share it in the hope that it will help.