Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Test Step

Test Description

Expected Results

Actual Results

Environment

Reference Ticket(s)

TC_01

dev/test

BE end-point, Dashboard table updates, First dashboard ticket

Scenario Description

Verify the user is displayed with the text “Search Results” title on the top left with a subheading below itdev/test

TC-137

Prerequisites

The user is on the “Personnel” screen.

Test Data

Action Steps

  1. View the top left of the table

  1. Search Results should be bolded

  2. The subheading should state “x members found with y filters applied” and the font should be smaller than the title “Search Results”

  3. The spacing between Search Results and x members should match the mock-ups

dev/test

TC_02

Scenario Description

Verify the first column “Name” is alphabetically sorted by the resource’s last name.

Prerequisites

The user is on the “Personnel” screen.

Test Data

Action Steps

  1. View the first column “Name”

  1. The user should be displayed with the resource’s last name in ALL CAPS followed by the first name.

  2. The list should be alphabetically sorted by last name.

  3. There should be no user-initiated sort.

TC_03

dev/test

Scenario Description

Verify the user can click on a resource’s name.

Scenario Description

Prerequisites

The user is on the “Personnel” screen.

Test Data

Action Steps

  1. Click on a resource’s name.

The user should be able to click on the name.

TC_04

dev/test

Scenario Description

Verify the user is displayed with 25 rows in the default table view.

Prerequisites

The user is on the “Personnel” screen.

Test Data

Action Steps

  1. View the number of rows being displayed.

The user should be displayed with 25 rows.

TC_05

dev/test

Scenario Description

Verify the user can increase the number of rows displayed to 50.

Prerequisites

The user is on the “Personnel” screen.

Test Data

Action Steps

  1. Click on the pagination drop-down and select 50.

The user should be displayed with 50 rows.

TC_06

dev/test

Scenario Description

Verify the user can increase the number of rows displayed to 100.

Prerequisites

The user is on the “Personnel” screen.

Test Data

Action Steps

  1. Click on the pagination drop-down and select 100.

The user should be displayed with 100 rows.

TC_07

dev/test

Scenario Description

Verify the user can click on a page number to be navigated to that page.

Prerequisites

Test Data

Test with different page numbers, the first, first + 1, last, last - 1

Action Steps

  1. Scroll to the bottom and click a page number.

The user should land on the selected page.

TC_08

dev/test

Scenario Description

Verify the user can navigate to the previous page.

Prerequisites

The user is on page 2 or higher.

Test Data

Action Steps

  1. Click on the back arrow on the pagination.

The user should be navigated to the previous page.

TC_09

dev/test

Scenario Description

Verify the user can navigate to the next page.

Prerequisites

The user is not on the last page.

Test Data

Action Steps

  1. Click on the forward arrow on the pagination.

  1. The user should be navigated to the next page.

TC_10

dev/test

Scenario Description

Verify the user can click on the double back arrow to land on the first page.

Prerequisites

Test Data

Action Steps

  1. Click on the double back arrow on the pagination.

The user should be navigated to the first page.

TC_11

dev/test

Scenario Description

Verify the user can click on the double forward arrow to land on the last page.

Prerequisites

Test Data

Action Steps

  1. Click on the double forward arrow on the pagination.

The user should be navigated to the last page.

TC_12

dev/test

Scenario Description

Verify the user stays on the current page if he clicks on the resource’s user profile.

Prerequisites

Test Data

Action Steps

  1. Navigate to a page other than page 1.

  2. Click on a resource’s name.

  1. The resource’s user profile should open in a new tab.

  2. The user should remain on the same table page.

TC_13

dev/test

Scenario Description

Verify the user is displayed with all ACTIVE resources by default.

dev/test

Prerequisites

The user is on the “Personnel” page.

Test Data

Action Steps

  1. View the table.

The user should be displayed with only ACTIVE resources by default.

TC_14

dev/test

Scenario Description

Verify the user is displayed with a “Show Inactive” toggle button for status on the top right of the table list and is able to turn it ON.

dev/test

Prerequisites

The user is on the “Personnel” page.

Test Data

Action Steps

  1. Click on the toggle button to display the INACTIVE resources as well.

The user should be able to turn the toggle ON and should be displayed with both active and inactive resources.

TC_15

dev/test

Scenario Description

Verify the user can turn the “Show Inactive” toggle OFF.

Prerequisites

The user is on the “Personnel” page.

Test Data

Action Steps

  1. Click on the Toggle to the OFF position.

The user should only be displayed with ACTIVE resources.

TC_16

dev/test

Scenario Description

Verify the user can view the 9 is displayed with all 10 columns on the dashboard table.

dev/test

Prerequisites

Test Data

Action Steps

The user is on the “Personnel” screen.

TC_17

Scenario DescriptionTest Data

Action Steps

  1. View the dashboard table list.

The user should be displayed with the following columns

Prerequisites

Test Data

Verify the dashboard table accurately displays the data and it matches with what is stored in the database.

dev/test

Action Steps

the 10 columns in the following order:

  1. Name

  2. Region

  3. Work Location

  4. Function (hidden in default view)

  5. Experience (hidden in default view)

  6. Availability Status

  7. Willingness to Travel

  8. Remote Only

  9. Classification

  10. Ministry

TC_17

dev/test

Scenario Description

Verify the user is displayed with the correct “Region” for each resource as the second column.

Prerequisites

The user is on the “Personnel” screen.

Test Data

Action Steps

  1. View the second column “Region”.

The user should be displayed with the correct Region name for the given resource, one value from the following seven:

HQ, CTL, NEA, NEW, SEA, SWE, VIC

TC_18

dev/test

Scenario Description

Verify the user is displayed with the correct “Work Location” for each resource as the third column and it corresponds to the correct “Region”.

Prerequisites

The user is on the “Personnel” screen.

Test Data

Action Steps

  1. View the third column “Work Location”

The user should be displayed with the correct “Work Location” for the given resource, one from the following, corresponding to the correct Region.

Image Added

TC_19

dev/test

Scenario Descriptiondev/test

Verify the user is not displayed with the Function column by default.

Function/Experience

Prerequisites

The user is on the “Personnel” screen.

Test Data

Action Steps

  1. View the table.

The user should not be displayed with the Function column by default.

TC_20

dev/test

Scenario Descriptiondev/test

Verify the user is not displayed with the Experience column by default.

Prerequisites

The user is on the “Personnel” screen.

Test Data

Action Steps

  1. View the table.

The user should not be displayed with the Experience column by default.

TC_21

dev/test

Scenario Descriptiondev/test

Verify the user is displayed with the correct value for “Availability Status” for each resource.

Availability Status Column

Prerequisites

The user is on the “Personnel” screen.

Test Data

Action Steps

  1. PENDING ON SCHEDULER

TC_22

dev/test

Scenario Descriptiondev/test

Verify the user is displayed with the correct value for “Willingness to Travel”.

Prerequisites

The user is on the “Personnel” screen.

Test Data

Fifth column - by default

Seventh column - when Function/Exp filters are applied

Action Steps

  1. View the “Willingness to Travel” column.

The user should be displayed with the correct “Yes/No” value for the given resource.

TC_23

dev/test

Scenario Descriptiondev/test

Verify the user is displayed with the correct value for the “Classification” column.

Prerequisites

The user is on the “Personnel” screen.

Test Data

Seventh column - by default

Ninth column - when Function/Exp filters are applied

Action Steps

  1. View the “Classification” column.

The user should be displayed with the correct value from one of the following two:

BCGEU, Excluded

TC_24

dev/test

Scenario Description

Verify the user is displayed with the correct acronym value for “Ministry” for each resource.

Prerequisites

The user is on the “Personnel” screen.

Prerequisites

Test Data

Eighth column - by default

Tenth column - when Function/Exp filters are applied

Action Steps

  1. View the “Ministry” column.

The user should be displayed with the correct value from one of the following 23:

  1. Agriculture and Food (AGRI)

  2. Attorney General (AG)

  3. Children and Family Development (MCF)

  4. Citizens' Services (CITZ)

  5. Education and Child Care (ECC)

  6. Emergency Management and Climate Readiness (EMCR)

  7. Energy, Mines and Low Carbon Innovation (EMLI)

  8. Environment and Climate Change Strategy (ENV)

  9. Finance (FIN)

  10. Forests (FOR)

  11. Health (HLTH)

  12. Housing (HOUS)

  13. Indigenous Relations & Reconciliation (IRR)

  14. Jobs, Economic Development and Innovation (JEDI)

  15. Labour (LBR)

  16. Mental Health and Addictions (MMHA)

  17. Municipal Affairs (MUNI)

  18. Post-Secondary Education and Future Skills (PSFS)

  19. Public Safety and Solicitor General (PSSG)

  20. Social Development and Poverty Reduction (SDPR)

  21. Tourism, Arts, Culture and Sport (TAC)

  22. Transportation and Infrastructure (MOTI)

  23. Water, Land and Resource Stewardship (WLRS)

TC_25

dev/test

Scenario Descriptiondev/test

Verify the dashboard table accurately displays the data and it matches with what is stored in the database.

Prerequisites

Test Data

Action Steps

  1. Reconcile the FE data with DB.

The user should be displayed with the values on the front-end as a match to what is stored in the database.