Common test Cases for Web pages (source:: 51testing--lxp1119216)

Purpose of this question: whether the interviewer is familiar with various test methods, has extensive experience in Web testing , is aware of web development, and the ability to design test case

The subject is still quite difficult, and it is difficult for the average person to answer the question well. First of all, you need to understand the needs of users, such as the login interface should be pop-up, or directly in the Web pageInside. The length of the user name, and the strength of the password (that is, it is not necessary how many bits, case, special character mash) and so on. There are, for example, the user's appearance of the interface is not a special requirement? (That is, whether you want a UI test).　　The rest is design use cases, equivalence classes, boundary values and so on. Keep in mind that any test, regardless of what is measured, begins with understanding the requirements. Functional Testing (function test )0. Do not enter anything, click the Submit button to see the prompt message. (Non-null check) 1. Enter the correct user name and password and click the Submit button to verify that you are logged in correctly. (normal input) 2. Enter the wrong user name or password, verify that the login fails, and prompt for the appropriate error message. (Error check) 3. Can you jump to the correct page (low) 4 If the login is successful. User name and password, if too short or too long, should be handled (security, password is too short if prompted) 5. Username and password, with special characters (such as spaces), and other non-English cases (whether filtered) 6. Remember the features of the user name 7. The function of the password cannot be logged after the login failed 8. The user name and password before and after the processing of a space 9. Password is encrypted display (asterisk dots, etc.) 10. The verification code involved, but also to consider whether the text is distorted too much to make it difficult to identify, consider the color (colour Whether to refresh or change a button is good 11. Registration on the login page, forgot password, log out with another account login and other links are correct 12. When you enter your password, you should have a message when the upper-case keyboard is open. Interface Testing (UI test)1. The layout is reasonable, 2 testbox and a button are aligned with the length of the 2.testbox and the button, whether the height of the composite requires 3. The design style of the interface is 4 consistent with the UI design style. The text in the interface is simple and easy to understand, without typos. Performance Test (performance test)1. Open the login page, it takes a few seconds 2. After entering the correct user name and password, login successfully jumps to the new page, no more than 5 seconds Safety Testing (security test)1. If the cookie generated after successful login is HttpOnly (otherwise it is easy to be hacked by the script) 2. Whether the user name and password are encrypted, send to Web server 3. Authentication of username and password should be verified by server side. Instead of just validating 4. User name and password in the input box of the client, you should block SQLInject attack 5. User name and password of the input box, should prohibit the input script (prevent XSS attack) 6. Number of error login limit (to prevent brute force) 7. Consider whether multiple users are supported to log on on the same machine; 8. Consider a user logging on on multiple machines Usability Testing (usability test)1. Whether the keyboard can be fully operated, whether there is a shortcut key 2. Enter the user name, password and press ENTER, whether you can log in 3. Whether the input box can be toggled with the TAB key Compatibility Testing (compatibility test)1. The main browser can be displayed normal function (ie,6,7,8,9, Firefox, Chrome, Safari, etc.) 2. Whether different platforms are working properly workLike what Windows, Mac 3. Whether the mobile device is working properly, such as the iphone, Andriod 4. Different resolutions Localization Testing (Localization test)1. The display of the page is correct in different language environments. Software-assisted testing (accessibility test) software accessibility testing refers to whether the test software provides sufficient accessibility to disabled users 1. can display normal under high contrast (for people with poor eyesight)

Common test Cases for Web pages (source:: 51testing--lxp1119216)