Each of the tests below relates to edituser test cases
Table 4. edituser Test Cases
TESTCASE | EVENTID | ACTION | EXPECTED_RESULTS |
---|---|---|---|
edituser | 1 | without filling in any of the fields, hit "search button" | all users returned in long form, total number of users at bottom |
edituser | 2 | enter invalid username in username field | no matches found |
edituser | 3 | enter invalid email address | no matches found |
edituser | 4 | enter invalid first name | no matches found |
edituser | 5 | enter invalid middle initial | no matches found |
edituser | 6 | enter invalid last name | no matches found |
edituser | 7 | enter partial or whole valid username, first name or last name | user is returned |
edituser | 8 | change email address field, update user | user data updated |
edituser | 9 | change first name, update user | user data updated |
edituser | 10 | change middle name, update user | user data updated |
edituser | 11 | change last name, update user | user data updated |
edituser | 12 | change user to administrator or to regular user | user administrative field updated |
edituser | 13 | enter data into users password fields, leave "change password?" pull down to "n" | form returned, no changes |
edituser | 14 | enter data into password fields, different passwords in the fields, "y" to change password | error returned saying passwords mis-matched |
edituser | 15 | no data entered into password fields, "y" to change password | error returned saying password cannot be blank |
edituser | 16 | enter data into password fields, same in both the fields, "y" to change password | password changed successfully |
edituser | 17 | hit delete user button | user is deleted, edit user search form is returned |