CCD Acceptance Test Cases

Acceptance Test CasesVersion 1.0

CCD Acceptance Test Cases

e-LockBox

<Team 10

<Team members and roles>

Cheng Zhang / Prototyper / Chief Developer
Guancheng Li / Project Manager/ Prototyper/ Developer
Yutong Guo / Operational Concept Engineer/ Developer/ Tester
Qing Wei / Life Cycle Planner/ Feasibility Analyst/ Developer
Si Zhao / Software Architect/ Tester

03/24/17

ACT_CCD_S17_T10_V1.0.docVersion Date: 03/24/2017

Acceptance Test CasesVersion 1.0

Version History

Date / Author / Version / Changes made / Rationale
03/24/17 / G.Li / 1.0 /

Modified the test cases

Initial Draft for CCD

CCD Acceptance Test Cases

Version History

Table of Contents

Table of Tables

1.Introduction

2.Test Identification

2.1TC-24 Login Security

2.2TC-23 Settings

2.3TC-01 Create User

2.4TC-02 View users

2.5TC-04 Activate User

2.6TC-05 Inactivate User

2.7TC-06 Create Case

2.8TC-10 Activate Case

2.9TC-11 Inactivate Case

2.10TC-07 View Case

2.11TC-0 Edit Case Profile

2.12TC-08 Create Account for Youth

2.13TC-18 Manage Work History

2.14TC- 17 Manage Education History

2.15TC-14 Manage Contact Information

2.16TC-15 Manage Additional Contacts

2.17TC-09 Delete Case

2.18TC-16 Manage Notes

2.19TC-19 Create Activity

2.20TC-20 View Activity

2.21TC-22 Delete Activity

2.22TC-27 Reset password by self

Table of Tables

Table 1: TC-24-01 Check Login Correctness

Table 2: TC-24-02 Check Login Completeness

Table 3: TC-24-03 Check Login with Wrong Information Input

Table 4: TC-24-04 Check Verification Code Correctness

Table 5: TC-24-05 Check Verification Code with Wrong Information Input

Table 6: TC-23-01 Set Program List

Table 7: TC-23-02 Set Document Type List

Table 8: TC-01-01 Check User Creation Correctness

Table 9: TC-01-03 Check User Creation with No Required Data Input

Table 10: TC-01-02 Check User Creation with Wrong Data Input Format

Table 11: TC-02-01 Check User Brief View Correctness

Table 12: TC-02-02 Check User Detailed View Correctness

Table 13: TC-04-01 Check User Activation Correctness

Table 14: TC-05-01 Check User Inactivation Correctness

Table 13: TC-06-01 Create a New Case

Table 16: TC-10-01 Activate a Case for Youth

Table 17: TC-11-01 Inactivate a Case for Youth

Table 14: TC-07-01 Check View Brief Case List

Table 15: TC-07-02 Check View Detailed Case Profile

Table 16: TC-12-01 Edit General Info of a Case

Table 17: TC-12-02 Assign a Case to a Case Manager

Table 18: TC-08-01 Create Account for Youth

Table 19: TC-18-01 Add Work History

Table 20: TC-18-02 View Work History

Table 21: TC-18-03 Edit Work History

Table 22: TC-18-04 Delete Work History

Table 23: TC-17-01 Add Education History

Table 24: TC-17-02 View Education History

Table 25: TC-17-03 Edit Education History

Table 26: TC-17-04 Delete Education History

Table 27: TC-14-01 Add Contact Information

Table 28: TC-14-02 View Contact Information

Table 29: TC-14-03 Edit Contact Information

Table 30: TC-14-04 Delete Contact Information

Table 31: TC-15-01 Add Additional Contact

Table 32: TC-15-02 View Additional Contact

Table 33: TC-15-03 Edit Additional Contact

Table 34: TC-15-04 Delete Additional Contact

Table 35: TC-09-01 Delete Case

Table 36: TC-16-01 Add Note

Table 37: TC-16-02 View Note

Table 38: TC-16-03 Edit Note

Table 39: TC-16-04 Delete Note

Table 44: TC-19-01 Create a New Activity

Table 45: TC-20-01 View Brief Activity Info

Table 46: TC-20-02 View Detailed Activity Info

Table 47: TC-22-01 Delete Activity

Table 48: TC-27-01 Reset Password

ACT_CCD_S17_T10_V1.0.docVersion Date: 03/24/2017

Acceptance Test CasesVersion 1.0

1.Introduction

The purpose of the document is to describe the acceptance criteria and its corresponding test cases for the core capabilities of the e-lockbox project which follows the win-win agreements documented in the winbook. The scope of these testing cases is to focus on the important functions related business operation which valued by our client, the Living Advantage Inc. All the tests under the acceptance test cases will be test on software of the application to make sure the functionalities of the application satisfy the requirements from our client.

ACT_CCD_S17_T10_V1.0.docVersion Date: 03/24/2017

Acceptance Test CasesVersion 1.0

2.Test Identification

The test case numbersare organized according to the function blocks which includes User Management, Case Management, Activity Management and System functions. While the acceptance cases are organized by the workflow of the system and in accordance with the User Manual.

2.1TC-24 Login Security

Table 1: TC-24-01Check Login Correctness

Test Case Number / TC-24-01 Check Login Correctness
Test Item / The user can log into system securely.
Test Priority / M
Pre-conditions / The user is valid.
Post-conditions / The verification code submitting page will be shown.
The verification code will be sent to user’s email box.
The verification code will be randomly generated and stored in database.
Input Specifications / Correct username and password.
Expected Output Specifications / The verification code submitting page will be shown.
The verification code will be sent to user’s email box.
Pass/Fail Criteria / Pass criteria:

The verification code submitting page is shown correctly.
An email with verification code will be sent to user’s email box.
Verification code is randomly generated.

Fail criteria:

The verification code submitting page is not shown correctly.
An email with verification code is not sent to user’s email box.
Verification code does not change.

Assumptions and Constraints /

“Valid” means the account/user is existed and activated.
The user email is authentic, i.e. the user will receive the email with verification code.

Dependencies / N/A
Traceability / WC_3935: As an admin, I can login with verification code securely.
WC_3978: As a case manager, I can login with verification code securely.
WC_3996: As staff, I can login with verification code securely.
WC_4005: As a youth, I can login with verification code securely.

Table 2: TC-24-02 Check Login Completeness

Test Case Number / TC-24-02 Check Login Completeness
Test Item / All types of user can log into system securely.
Test Priority / M
Pre-conditions / The user is valid.
Post-conditions / The verification code submitting page will be shown.
The verification code will be sent to user’s email box.
The verification code will be randomly generated and stored in database.
Input Specifications / Correct username and password.
Expected Output Specifications / The verification code submitting page will be shown.
The verification code will be sent to user’s email box.
Pass/Fail Criteria / Pass criteria:

All types of user successfully log in and redirect to verification code.
If verification code is correct, the user dashboard should be shown accordingly.

Fail criteria:

Some types of user cannot log in.
If verification code is correct, the user dashboard is not shown correctly.

Assumptions and Constraints /

“Valid” means the account/user is existed and activated.
The user email is authentic, i.e. the user will receive the email with verification code.

Table 3: TC-24-03 Check Login with Wrong Information Input

Test Case Number / TC-24-03 Check Login with Wrong Information Input
Test Item / Invalid user log into system.
Test Priority / M
Pre-conditions / The user/account is invalid.
Post-conditions / An error message will be shown properly.
Input Specifications / Invalid username and password.
Expected Output Specifications / An error message “The account is not activated” will be shown if an existed but no valid user is trying to log in.
An error message “The username and password do not match” will be shown if an account is not existed, or the password input is incorrect.
Pass/Fail Criteria / Pass criteria:

The error message should be shown properly and correctly.
The user cannot visit verification code page.

Fail criteria:

The error message is not shown or incorrect.
The user can log into the system even with an invalid username or password.

Assumptions and Constraints /

“Invalid” means the account/user is not existed, or existed but not activated, or the password is incorrect.

Table 4: TC-24-04 Check Verification Code Correctness

Test Case Number / TC-24-04 Check Verification Code Correctness
Test Item / The user can visit dashboard.
Test Priority / M
Pre-conditions / The user/account is valid.
Post-conditions / The dashboard is correctly redirected.
The dashboard’s information is correctly shown.
The session is correctly created.
Input Specifications / Correct username, password and verification code.
Expected Output Specifications / The dashboard is correctly redirected.
The dashboard’s information is correctly shown.
Pass/Fail Criteria / Pass criteria:

All types of user can be redirected to dashboard after correct verification code is submitted.
The dashboard is correctly redirected.
The user’s session is successfully created.
The information on dashboard is correctly shown, which means the session is created and correct.

Fail criteria:

Page does not redirect to dashboard even though correct verification code is submitted.
The user’s session is not created even though he/she is redirected to user dashboard page.
The information on dashboard is not shown correctly, which means the session is created but not correct.

Assumptions and Constraints /

“Valid” means the account/user is existed and activated.
The user email is authentic, i.e. the user will receive the email with verification code.

Dependencies / TC-24-01; TC-24-02; TC-24-03;
Traceability / WC_3935: As an admin, I can login with verification code securely.
WC_3978: As a case manager, I can login with verification code securely.
WC_3996: As staff, I can login with verification code securely.
WC_4005: As a youth, I can login with verification code securely.

Table 5: TC-24-05 Check Verification Code with Wrong Information Input

Test Case Number / TC-24-05 Check Verification Code with Wrong Information Input
Test Item / The user try to visit dashboard with invalid verification.
Test Priority / M
Pre-conditions / The user/account is valid.
Post-conditions / An error message should be shown correctly.
The session cannot be created.
Input Specifications / Correct username, password, but invalid verification code.
Expected Output Specifications / An error message “Invalid verification code” should be shown on verification code submitting page.
The page should redirect to log in page if user submits invalid verification code 3 times, with an error message “Too many times trying, please login again”.
Pass/Fail Criteria / Pass criteria:

An error message should be shown correctly.
The page should redirect to log in page if user submits invalid verification code 3 times.
The session should not be created, which means the user cannot visit their dashboard page by URL.

Fail criteria:

Any failure on pass criteria.

Assumptions and Constraints /

“Valid user/account” means the account/user is existed and activated.
“Invalid verification code” means wrong verification code, or obsolete verification code.

2.2TC-23 Settings

Table 6: TC-23-01SetProgram List

Test Case Number / TC-23-01 Set Program List
Test Item / Test whether admin can successfully set program list, and the program list should be related to case when creating or editing cases.
Test Priority / M (Must have)
Pre-conditions / The admin has logged into the system.
Post-conditions / A program list should be set according to the changes, and related usages should also be changed.
Input Specifications / Each program name is required, which will be shown in the program list finally.
Expected Output Specifications / The program list should be shown correctly as the result of changes.
Pass/Fail Criteria / Pass criteria:

An updated program list should be generated and saved.
Every usage of program list should be printed correctly.

Fail criteria:

Any failure in pass criteria.

Assumptions and Constraints /

Only when the user is admin.

Dependencies / TC-24-01; TC-24-02; TC-24-03; TC-24-04; TC-24-05;
Traceability / WC_3931: As an admin, Ican set program list.

Table 7: TC-23-02Set Document Type List

Test Case Number / TC-23-02 Set Document Type List
Test Item / Test whether admin can successfully set document types, and the document type list should be related to case when managing case documents.
Test Priority / M (Must have)
Pre-conditions / The admin has logged into the system.
Post-conditions / A document type list should be set according to the changes, and related usages should also be changed.
Input Specifications / The document type name and its abbreviation are required.
Expected Output Specifications / The document type list should be generated and saved.
Pass/Fail Criteria / Pass criteria:

An updated document type list should be generated and saved.
Every usage of document type list should be printed correctly.

Fail criteria:

Any failure in pass criteria.

Assumptions and Constraints /

Only when the user is admin.

Dependencies / TC-24-01; TC-24-02; TC-24-03; TC-24-04; TC-24-05;
Traceability / WC_3932: As an admin, I can set document types.

2.3TC-01 Create User

Table 8: TC-01-01 Check User Creation Correctness

Test Case Number / TC-01-01 Check User Creation Correctness
Test Item / This tests that an admin can create an admin, case manager, or staff account.
Test Priority / M (Must have)
Pre-condition / An admin has logged into the system and is at user creation page.
Post-conditions / An adminis at user creation page with a success message.
Input Specifications / Input required information in right format, including email address, password, password confirmation, first name, last name, and user level such as admin, case manager, staff.
Expected Output Specifications / A success message appears - User successfully created and activated.
Pass/Fail Criteria / Pass Criteria:

A user has been created and activated.
A verification code has been initialized for the new created user.
A profile has been initialized for the new created user.
The new created user can log into the system with matched username, password, and verification code.

Fail Criteria:

Any failure in Pass Criteria.

Assumptions and Constrains /

Admin cannot create youth user account in user management.

Dependencies / TC-24-01; TC-24-02; TC-24-03; TC-24-04; TC-24-05;
Traceability / WC_3920: As an admin, I can create a user account, including admin, case manager, and staff.

Table 9: TC-01-03 Check User Creation with No Required Data Input

Test Case Number / TC-01-02 Check User Creation with Wrong Data Input Format
Test Item / This tests that an admin user would fail to create a user if they input data in wrong format.
Test Priority / S (Should have)
Pre-condition / An admin has logged into the system and is at user creation page.
Post-conditions / An adminis at user creation page with error messages.
Input Specifications /

Input an email address in wrong format.
Input an existing email address.
Input password in wrong format.
Input not-matched password confirmation.

Expected Output Specifications /

Error message appears.
The email must be a valid email address.
The email has already been taken.
The password must be at least 6 characters.
The password confirmation does not match.

Pass/Fail Criteria / Pass Criteria:

Input an email address in wrong format, the error message should be that the email must be a valid email address.
Input an existing email address, the error message should be that the email address has already been taken.
Input password with less than 6 characters, the error message should be that the password must be at least 6 characters.
Input not-matched password confirmation, the error message should be that the password confirmation does not match.

Fail Criteria:

Any failure in Pass Criteria.

Assumptions and Constrains /

Admin cannot create youth user account in user management.

Dependencies / TC-24-01; TC-24-02; TC-24-03; TC-24-04; TC-24-05;
Traceability / WC_3920: As an admin, I can create a user account, including admin, case manager, and staff.

Table 10: TC-01-02 Check User Creation with Wrong Data Input Format

Test Case Number / TC-01-03 Check User Creation with No Required Data Input
Test Item / This tests that an admin would fail to create a user if they do not input required field.
Test Priority / S (Should have)
Pre-condition / An admin has logged into the system and is at user creation page.
Post-conditions / An admin is at user creation page with error messages.
Input Specifications /

Not input email address.
Not input password.
Not input password confirmation.
Not input first name.
Not input last name.

Expected Output Specifications /

Error message appears.
The email field is required.
The password field is required.
The password confirmation does not match.
The first name field is required.
The last name field is required.

Pass/Fail Criteria / Pass Criteria:

Not input email address, the error message should be that the email field is required.
Not input password, the error message should be that the password field is required.
Not input password confirmation, the error message should be that the password confirmation does not match.
Not input first name, the error message should be that the first name field is required.
Not input last name, the error message should be that the last name field is required.

Fail Criteria:

Any failure in Pass Criteria.

Assumptions and Constrains /

Admin cannot create youth user account in user management.

Dependencies / TC-24-01; TC-24-02; TC-24-03; TC-24-04; TC-24-05;
Traceability / WC_3920: As an admin, I can create a user account, including admin, case manager, and staff.

2.4TC-02 View users

Table 11: TC-02-01 Check User Brief ViewCorrectness

Test Case Number / TC-02-01 Check User BriefView Correctness
Test Item / This tests that an admin, case manager or staff can view brief user profile in a table.
Test Priority / M (Must have)
Pre-condition / An admin, case manager or staff has logged into the system and is at view user page.
Post-conditions / An admin, case manager or staff can see a list of users.
Input Specifications / N/A
Expected Output Specifications / Brief user information are shown in a table.
Pass/Fail Criteria / Pass Criteria:

Correct user information is showed in right format.

Fail Criteria:

Any failure in Pass Criteria.

Assumptions and Constrains /

Youth cannot view user profile.

Dependencies / TC-24-01; TC-24-02; TC-24-03; TC-24-04; TC-24-05; TC-01-01; TC-01-02; TC-01-03;
Traceability / WC_3923: As an admin, I can view brief user profile in a table.
WC_3968: As a case manager, I can view brief user profile in a table.
WC_3988: As staff, I can view brief user profile in a table.

Table 12: TC-02-02 Check User Detailed ViewCorrectness