Shulou(Shulou.com)06/02 Report--

This article introduces the relevant knowledge of "software test case analysis". In the operation process of actual cases, many people will encounter such difficulties. Next, let Xiaobian lead you to learn how to deal with these situations! I hope you can read carefully and learn something!

Identify specific needs:

There's a login page, there's an account and a password input box, a submit button.

The purpose of this investigation:

1. Understand the needs (everything starts with understanding the needs);

2, whether there is the ability to design Test cases

3. Whether you are familiar with various test methods;

4. Whether you have rich experience in Web testing;

5. Whether you understand Web development;

Analysis requirements:

1, login interface should be pop-up window type, or directly in the web page inside;

2. Account length and password strength (such as how many digits are required, case-sensitive, special character mix, etc.);

3. Is there any special requirement for interface beauty? (i.e. whether to conduct UI testing);

4、····

Use Case Design:

After the test requirements analysis is completed, the use case design begins, which can be considered mainly from the following aspects:

Function Test

1. Enter the correct account and password, click the Submit button to verify whether you can log in correctly. (normal input)

2, enter the wrong account or password, verification login will fail, and prompt the corresponding error message. (Error checking)

3. Can you jump to the correct page after successful login (low)

4. Account number and password, if it is too short or too long, what should be done (security, whether there is a prompt when the password is too short)

5. Account number and password, with special characters (such as spaces), and other non-English situations (whether filtered)

6, remember the function of the account

7, login failed, can not record the password function

8. Handling of blank spaces before and after account number and password

9. Whether the password is encrypted (asterisk dot, etc.)

10. If Captcha is involved, it is also necessary to consider whether the text is excessively distorted, which makes it difficult to identify, consider the color (colorblind users), refresh or change a button, whether it is easy to use

11. Whether the links in the login page such as register, forget password, logout and login with another account are correct

12. When entering the password, there should be prompt information when the capital keyboard is turned on.

13. Enter nothing, click the submit button and see the prompt information. (Non-empty check)

UI Test:

1. Whether the layout is reasonable, whether the two Testboxes and one button are aligned

2. Whether the length and height of Testbox and button are compound requirements

3. Whether the design style of the interface is unified with the design style of the UI

4. The text in the interface is simple and easy to understand, without typos.

Performance Test:

1. Open the login page, it takes a few seconds

2. After entering the correct account and password, log in successfully and jump to the new page within 5 seconds.

Security Test:

1. Whether the cookies generated after successful login have HttpOnly(reduce the risk of script theft)

2. Whether the account number and password are encrypted and sent to the Web server

3, account and password verification, should be verified with the server side, and not only in the client side with JavaScript verification

4, account and password input box, should shield SQL injection attacks

5, account and password input box, should prohibit the input of scripts (to prevent XSS attacks)

6. Limit the number of wrong logins (to prevent brute force cracking)

Consider whether to support multiple users logging in on the same machine;

Consider a user logging in on multiple machines

Usability Test:

1. Whether it can be operated by keyboard and whether there are shortcut keys

2. Enter the account number, press Enter after the password, whether you can log in

3. Whether the input box can be switched with Tab key

Compatibility Test:

1. Whether it can be displayed normally under mainstream browsers (IE6~11, Firefox, Chrome, Safari, etc.)

2, whether different platforms can work properly, such as Windows, Mac

3. Whether it works normally on mobile devices, such as iPhone, Android

4. Different resolutions

The localization test:

1. Whether the page is displayed correctly in different language environments.

Software Accessibility Test:

Software accessibility testing refers to testing whether software provides adequate accessibility to disabled users

1. Can it be displayed normally under high contrast (used by people with poor vision)

"Software test case analysis" content is introduced here, thank you for reading. If you want to know more about industry-related knowledge, you can pay attention to the website. Xiaobian will output more high-quality practical articles for everyone!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.