1. Design test cases according to different pages

The above picture is for the test of a website, and the corresponding test cases are designed according to the different pages.

log in page

User information list

user edit page

user update page

2. Design test cases according to different purposes

In the same way, we can also test the response of a website in the following way

Functional testing
   Whether the website has achieved the expected function

Ease of use test:
   When inputting information, whether the mouse can be automatically positioned to the input column
   after the account number or password is entered incorrectly, and whether the original incorrect content will be automatically cleared

Performance testing        The response time of
   multiple machines logging in to the page at the same time    Loading of the page in a weak network environment

Response time for a single user login page

    At the same time,
is there a risk of memory leaks when a large number of users log in and out of the server?

Interface test
   The color of the interface The
   background picture of the interface shows
   whether the text of the interface is correct Whether
   the layout of the interface is reasonable and meets expectations
   Whether the interface is user-friendly

Security test
Whether the password is displayed in dark text when entering the password Whether
   the user password storage method
   will be leaked due to bugs, or inadvertently leaking user information
   permission issues
       Non-administrators cannot log in to the background system
       and have no response authority, and users cannot be changed
   SQL injection Whether the data is encrypted
   when the front-end and back-end are interacting with
   each other Whether to limit the number of user login errors to prevent
       retaining and cracking
   the password box Whether to prohibit copying and pasting
   the password is too simple Whether there is a security prompt Whether the
   password is time-sensitive and
       the user has not changed the password for a long time Whether there will be a reminder to change the password
   Whether to encrypt the implicit data on the page source interface
   Mutual exclusion of login
       The same user logs in on multiple terminal browsers
       The same user logs in on the same terminal with multiple browsers

Whether the software compatibility test
   supports
       the display of multiple terminals and the mobile phone
       The overall interface compatibility
   is different. The browsing effect    is different .
       Firefox,
       Google
       Edge
       , and other domestic browsers.        Compatibility of the new version with the old version.        Whether the old version can normally access        the old version. Is the user experience consistent? consistent before

Household registration management system test case