1 "Given that the admin wants to add a user
When the admin clicks the add button
Then these fields should be seen in the add user form:
First Name
MIddle Name
Last Name
Email address
User Role
DateOfBirth
address
Gender
DateEmployed"
2 "Given that the admin wants to add a user
When the admin clicks the add user button
Then fields should still follow proper validation and limitation of text input in each field
-First Name (30 characters)
-Middle Name (30 characters)
-Last Name (30 characters)
-Email address (60 characters)
-User Role (Dropdown with options to choose from)
-address (60 characters)
-Date of Birth (Dropdown Calendar)
-Gender (Dropdown)
-Date Employed (Dropdown Calendar)"
3 "Given that the admin will create an employee/property custodian account
When the admin created the account successfully
Then an email notification (with account credentials <email & auto generated password>) should be sent to user"
4 "Given that the admin will create an account profile
When admin filled up email address field with existing email (registered email already by other user)
Then error message should be displayed that email has been used."
5 "Given that the admin will create a property custodian account
When the admin assigned ""Property custodian"" role to a profile
Then property custodian user should be created"
6 "Given that the admin will create an employee account
When the admin assigned ""Employee"" role to a profile
Then user account should be created"
7 "Given that the admin will create an account with admin privileges
When the admin assigned ""Admin"" role to a profile
Then Admin account should be created"
8 "Given that the admin wants to add a user
When the admin successfully add a new user
User List should be updated with the new user"
9 "Given that the user is in the ""New Employee"" form
When the user accidentally clicks the back button
Then the fade effect when opening the ""New Employee"" form should also be gone.
Note:
See Defect at Sprint 3: ID1515"
10 "Given that the user is in the ""New Employee"" form and has clicked the DatePicker field
When the user accidentally clicks the back button
Then the DatePicker should not be displayed anymore
Note:
See Defect at Sprint 3: ID1514"
11 "Given that the user wants to add user
When the user registers but using an already registered email
Then a tooltip should be displayed that email entered is already used by another user (Use globalzeal email)
Note:
See Defect at Sprint 3: ID1513 (This is the defect that when you use the same email address of an existing user, the newly edited user displays NaN values on all fields)"
12 "Given that the user wants to add a user
When the user registers but accidentally entered invalid values on the DateOfBirth or DateEmployed field
Then the user should be prompted that email entered is already used by another user
Note:
See Defect at Sprint 2: ID1513 (This is the defect that when you enter invalid characters into the date picker, the newly edited user displays NaN values on all fields)"
13 Remove prompt if sure on adding a user