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

(1) permission: after giving a person the corresponding permission, check whether the person has this permission on the interface, and log in as this person to verify whether the permission setting is correct (whether it can exceed the permission granted).

(2) check whether users with different permissions have operations consistent with their permissions when logging in; check whether users who do not have permissions have corresponding permissions

(3) user: after deleting the user, check whether the user can still log in; re-enter the user to see if there are any errors reported, and whether the user has been logged in the database

(3) whether the user who is deleted and re-added has the previous permissions, change the user's attributes (including permissions) to see the impact on the permissions.

(3) whether the user is allowed to log in without authorization.

(3) add users (with identification or number): the identity is the same, but the user name is different; the same identity, the same user name; different identity, the same user name; different identity, different user name.

(3) whether long user name and long password can be added, and if allowed, whether new users can log in correctly.

(3) can you add users whose information is empty (including empty user name, password, empty user name, non-empty password, non-empty user name and empty password).

(3) user fill in unit: the lower layer can add users whose unit is the upper unit, and log in with this unit after adding to check whether the unit is blank.

(3) whether the login user can modify his (or other people's) information and delete himself (or others).

(3) the impact of modifying the user's information (including permissions, passwords, basic information, etc.) on other modules; after changing the password, determine whether the password is consistent with the modified password

(4) permission group test.

(4) add a permission and add a permission user, and then delete whether the permission restricts "cannot delete the used role", and cannot be deleted directly until the permission user is deleted. If there is no restriction, the permission management will be deleted. The user's saved permission is empty, and an error will occur when logging in.

(7) whether the program can correctly handle the deletion of workgroups or roles that contain users when there is a workgroup or role management.

(8) after re-registering the system to change the login identity, log in to see whether the program can be executed correctly and whether the authority is correct.

(9) whether changing certain settings will affect the settings of people with superior authority and peer authority.

(10) query unit: log in with this unit and the unit you can see can only be your own unit; use admin login to modify the query unit to save, and then click to see whether only the unit just selected is displayed.

(11) change of group permissions.

(12) whether users can belong to multiple groups at the same time, and whether the permissions of each group can be crossed.

(13) whether the system administrator modifies some data and updates it when logging in as someone else.

(14) whether the system deletes the special user of the system administrator or modifies the password of the system administrator, and deletes or modifies the actual situation of the system

(15) override all permission settings of the system.

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.