< test case design > General test methods for user and rights management functions

1) to give a person the appropriate permissions, in the interface to see if this person has this permission, and as the person logged in, verify that the permissions are set correctly (can exceed the given permissions);

2) Delete or modify the permission of the person who has logged into the system and is in operation, whether the program can be handled correctly;

3) Re-registration system changes login status and then log in, to see if the program can be executed correctly, with the correct permissions;

4) In the case of Working group or role management, delete the workgroup or role that contains the user, whether the program can be handled correctly;

5) Different rights users login to the same system, the scope of permission is correct;

6) Overwrite the system all permission setting;

7) can add the user with empty information (including blank username and empty password, NULL username non-null password, non-empty username and empty password);

8) can add long user name and long password, if allowed, new users can log in correctly;

9) Whether the system allows to remove the system administrator this special user or modify the system administrator password, delete or modify the actual situation of the system;

10) The login user can modify their own permissions;

11) Add user (with ID or number): The identity is the same, the user name is different, the identity is the same, the user name is the same, the identity is different, the user name is the same, the user name is different;

12) The user can modify the information of himself (or other person), delete himself (or other person);

13) Modify the user's information (including permissions, passwords, basic information, etc.), the impact on other modules;

14) Modify the user information: the modified user information is the same as the existing user information, the modified user information and the existing user information is different;

15) do not give the user authorization, whether to allow login;

15) If certain settings are changed, will it affect the settings of people with higher authority and the same authority;

16) The system administrator has modified some data, whether the data changes when logged in as a different person;

17) If the user can belong to more than one group at the same time, the permissions of each group can be crossed, whether the user re-added after the deletion has previous permissions, and changes the user's attributes (including permissions) to see if the permissions are affected.

< test case design > General test methods for user and rights management functions