Test a web page login interface: http://www.cnblogs.com/I-am-Betty/p/3566411.html
Interface test: http://blog.csdn.net/xiaoyida11/article/details/50619750
How to test a web login interface
======================================================
Functional testing, UI testing, performance testing, security testing, usability testing, compatibility testing
======================================================
Specific requirements: There is a landing page, (if there are 2 textboxes and a submit button on it. Please design more than 30 test cases for this page. )
The purpose of this question is: whether the interviewer is familiar with various testing methods, whether he has rich experience in Web testing, whether he understands Web development, and the ability to design test cases
This question is quite difficult, and it is difficult for ordinary people to answer this question well.
First of all, you need to understand the needs of users, such as whether this login interface should be a pop-up window or directly in the web page. For the length of the user name, and the strength of the password (that is, how many digits, case, special characters must be mixed and matched), etc. For example, do users have special requirements for the aesthetics of the interface? (ie whether to do UI testing). The rest is design use cases , equivalence classes, boundary values, etc.
Please keep in mind that any test, no matter what it is, starts with understanding the requirements.
Function test
0. Enter nothing, click the submit button, and see the prompt information.
1. Enter the correct user name and password, and click the submit button to verify that you can log in correctly.
2. If you enter an incorrect username or password , the verification login will fail, and a corresponding error message will be prompted.
3. Can you jump to the correct page after successful login?
4. What should be done if the username and password are too short or too long?
5. Username and password with special characters (such as spaces), and other non-English cases
6. The function of remembering the username
7. After the login fails, the function of the password cannot be recorded
8. Handling of spaces before and after username and password
9. Whether the password is encrypted and displayed (asterisk dots, etc.)
10. If the verification code is involved, it is also necessary to consider whether the text is too distorted, which makes it difficult to identify, consider the color (color-blind users), and whether the refresh or change a button is easy to use
11. Are the links on the login page, such as registering, forgetting password, logging out and logging in with another account, etc. are correct?
12. When entering the password, there will be a prompt message when the uppercase keyboard is turned on .
UI Test
1. Whether the layout is reasonable, whether the 2 testboxes and one button are aligned
2. Whether the length and height of testbox and button are compound requirements
3. Is the design style of the interface consistent with the design style of the UI ?
4. The text in the interface is concise and easy to understand, and there are no typos.
performance test
1. Open the login page, it takes a few seconds
2. After entering the correct user name and password, the login successfully jumps to a new page, within 5 seconds
Security test
1. Whether the cookie generated after successful login is httponly ( otherwise it is easy to be stolen by script )
2. Whether the username and password are encrypted and sent to the web server
3. The verification of username and password should be verified on the server side, not just with javascript on the client side
4. The input box of username and password should block SQL injection attacks
5. The input box for username and password should be prohibited from entering scripts (to prevent XSS attacks)
6. Limit the number of wrong logins (to prevent brute force cracking)
7. Consider whether to support multiple users logging in on the same machine;
8. Consider a user logging in on multiple machines
Usability Test
1. Is it possible to use the keyboard to operate, and whether there are shortcut keys
2. Enter the username and password and press Enter to see if you can log in
3. Can the input box be switched with the Tab key?
Compatibility Test _
1. Whether it can be displayed normally in mainstream browsers ( IE, 6, 7, 8, 9, Firefox, Chrome, Safari, etc.)
2. Whether different platforms can work normally, such as Windows, Mac
3. Whether it works normally on mobile devices, such as Iphone, Andriod
4. Different resolutions
Localization test ( Localization test )
1. Check whether the page is displayed correctly in different language environments.
Software accessibility test ( Accessibility test )
Software accessibility testing refers to testing whether software provides adequate accessibility for disabled users
1. Can it be displayed normally under high contrast (for people with poor eyesight)