Page Comparison

Test Step	Test Description	Expected Results	Environment	Reference Ticket(s)
TC_01			test	New Applicant
Scenario Description	Verify the user is displayed with the “New” label next to the resource name for newly submitted applications
Prerequisites	The user is logged in to the app as a coordinator.
Test Data
Action Steps	Move the toggle to inactive. View the dashboard table.	The user should be displayed with all new resources first, labelled as “New” - highlighted in blue. The status of “New” resources is “inactive” by default.
TC_02
Scenario Description	Verify the user is displayed with an unchecked checkbox to indicate new user on the user’s profile.
Prerequisites	The user is logged in to the app as a coordinator.
Test Data
Action Steps	Click on a new resource’s name. View the user profile.	The user should be displayed with an unchecked checkbox to indicate new user on the user’s profile.

TC_03
Scenario Description	Verify the user is displayed with a warning pop-up if the checkbox is checked to indicate the profile has been reviewed and accepted by a TEAMS Coordinator.
Prerequisites	The coordinator is on the new resource’s profile.
Test Data
Action Steps	Check the checkbox next to the resource’s status.	The user should be displayed with a warning will pop up to alert that this cannot be undone. This box being checked should indicate that a new user has been reviewed an accepted by a teams coordinator.		(ROLES: coordinator: read/write, logsOff: read)

TC_04
Scenario Description	Verify the user is displayed with a notes section and has read/write access.
Prerequisites	The coordinator is on the new resource’s profile.
Test Data
Action Steps	View the notes section. Create/update a note.	The user should be able to read/write notes.

TC_05
Scenario Description	Verify the user can delete a note.
Prerequisites	The coordinator is on the new resource’s profile.
Test Data
Action Steps	View the notes section. Delete a note.	The user should be able to delete a note.
TC_06
Scenario Description	Verify the user is displayed with an active/inactive toggle button.
Prerequisites	The coordinator is on the new resource’s profile.
Test Data
Action Steps	View the active/inactive toggle.	The user should be displayed with the active/inactive toggle button.
TC_07			test
Scenario Description	Verify the user is able to set a resource as active.
Prerequisites	The coordinator is on the new resource’s profile.
Test Data	Test with an active and inactive users.
Action Steps	View the active/inactive toggle. Change it to active.	The user should be able to change the resource’s status to active.


TC_08
Scenario Description	Verify the user is able to set a resource as inactive.
Prerequisites	The coordinator is on the new resource’s profile.
Test Data
Action Steps	View the active/inactive toggle. Change it to inactive.	The user should be able to change the resource’s status to inactive.


TC_09			test
Scenario Description	Verify the user is not displayed with the “New” resources.
Prerequisites	The user is logged in to the app as a logistics officer.
Test Data
Action Steps	View the dashboard table.	The user should not be displayed with new resources.
TC_10
Scenario Description	Verify the user is not displayed with the resource’s status (new, active, inactive) on the user’s profile.	Jira ticket “This box being checked indicates that a new user has been reviewed an accepted by a teams coordinator (ROLES: coordinator: read/write, logsOff: read)”
Prerequisites	The user is logged in to the app as a logistics officer.
Test Data
Action Steps	Click on a new resource’s name. View the user profile.	The user should not be displayed with the resource’s status (new, active, inactive) on the user’s profile.


TC_11
Scenario Description	Verify the user is not displayed with the active/inactive toggle on a user’s profile.
Prerequisites	The user is logged in to the app as a logistics officer.
Test Data
Action Steps	Click on a new resource’s name. View the user profile.	The user should not be displayed with the active/inactive toggle on a user’s profile.



TC_12
Scenario Description	Verify the user is displayed with a notes section and only has read access??	According to Jira ticket 257, “ there should be an additional notes field for coordinators only (ROLES: coordinator: read/write, logsOff: none)
Prerequisites	The user is logged in to the app as a logistics officer.
Test Data
Action Steps

TC_13
Scenario Description
Prerequisites
Test Data
Action Steps

TC_14
Scenario Description
Prerequisites
Test Data
Action Steps

TC_15
Scenario Description
Prerequisites
Test Data
Action Steps


TC_16
Scenario Description
Prerequisites
Test Data
Action Steps
TC_17
Scenario Description
Prerequisites
Test Data
Action Steps

TC_18
Scenario Description
Prerequisites
Test Data
Action Steps


TC_19
Scenario Description
Prerequisites
Test Data
Action Steps

TC_20
Scenario Description
Prerequisites
Test Data
Action Steps
TC_21
Scenario Description
Prerequisites
Test Data
Action Steps
TC_22
Scenario Description
Prerequisites
Test Data
Action Steps

TC_23
Scenario Description
Prerequisites
Test Data
Action Steps

TC_24
Scenario Description
Prerequisites
Test Data
Action Steps

TC_25
Scenario Description
Prerequisites
Test Data
Action Steps
TC_26
Scenario Description
Prerequisites
Test Data
Action Steps

...

Versions Compared

Old Version 1

New Version Current

Key