Test Plan for Talent Cloud App MVP

Dev environment: https://tcloud-client-cd4869-dev.apps.gold.devops.gov.bc.ca

Test environment: https://tcloud-client-cd4869-test.apps.gold.devops.gov.bc.ca

Project Overview:

The project aims to deliver a Minimum Viable Product (MVP) of the Talent Cloud App by mid-March 2024. The app is designed to assist BC government employees, especially TEAMS coordinators, in finding and deploying TEAMS members' talent during emergencies and disasters. Additionally, the project includes the delivery of an updated intake form for BC employees to apply to EMCR TEAMS, ensuring a seamless user experience.

Project Overview - Release 3: Expansion of the CORE Product for Recommitment and Member Agency - January 2025:

The objective of this project’s release is to implement an automated notification and dashboard system that supports the 2025 CORE Team recommitment process. This system aims to streamline the workflow, reduce administrative burden, and enhance visibility for both CORE Team members and their supervisors. The project will automate reminders, track progress, and provide tools for both CORE Team members and supervisors to manage the recommitment process effectively.

Objectives:

1. Ensure the Talent Cloud App MVP is functional and meets the specified requirements.

2. Verify that TEAMS coordinators and regular IDIR users can authenticate and access the app.

3. Validate the search and filter capability on the dashboard screen.

4. Confirm the functionality of the dashboard table view, displaying TEAMS resources information.

5. Test navigation to the profile detail page and the ability to view user profiles.

6. Verify the functionality of updating a user's schedule by updating their availability status.

Objectives - Release 3

• Verify Automated Email Functionality:

  • Ensure that automated emails are sent correctly on the specified dates (January 20, 27, February 3, 10, 17, and 21).

  • Confirm that emails are correctly formatted and contain the necessary information.

• Test Supervisor Dashboard:

  • Validate that supervisors can successfully approve or decline recommitment requests.

  • Ensure that declined requests allow supervisors to provide a reason, which is visible only to them and coordinators.

• Test CORE Team Member Dashboard:

  • Confirm that CORE Team members can initiate the recommitment process and complete required actions.

  • Ensure members can update their personal information, availability, and indicate their intention to recommit or not.

  • Verify that members who choose not to recommit are prompted to provide a reason, with the data being visible only to coordinators.

Test Phases:

Phase 1: Authentication and Access Control

• Objective: Validate user authentication and access control for coordinators and regular IDIR users.

1.1 Coordinator Authentication

• Verify that TEAMS coordinators can successfully log in using their credentials managed by KeyCloak.

• Confirm that coordinators have access to coordinator-specific features.

1.2 Regular IDIR User Authentication

• Verify that regular IDIR users can successfully log in using their credentials managed by KeyCloak.

• Confirm that regular IDIR users have access to user-specific features.

Phase 2: Dashboard Functionality

• Objective: Validate the search and filter capability on the dashboard screen.

2.1 Search Functionality

• Test the ability to search for TEAMS resources based on various criteria.

• Confirm that search results are accurate and responsive.

2.2 Filter Functionality

• Test the filter functionality to narrow down the displayed resources.

• Verify that filters work as intended and produce the expected results.

Phase 3: Dashboard Table View

• Objective: Confirm the functionality of the dashboard table view.

3.1 Information Display

• Verify that the dashboard table view accurately displays information regarding TEAMS resources.

• Confirm that the displayed information aligns with the search and filter criteria.

• Confirm that the information presented corresponds accurately to the data stored in the database.

Phase 4: Profile Detail Page

• Objective: Test navigation to the profile detail page and the ability to view user profile and update schedule.

4.1 Navigation

• Verify that clicking on a resource's name navigates the user to the profile detail page.

• Confirm that the navigation is smooth and efficient.

4.2 View User Profile

• Test the ability to view detailed information about a TEAMS resource.

• Confirm that all relevant information is displayed accurately.

4.3 Update User Schedule

• Test the ability to update a user's schedule by changing their availability status.

• Confirm that the three status options (available, unavailable, and deployed) function correctly.

Test Phase - Release 3

Automated Email Notification - Initial Reminder (January 20)

Objective: Verify that the first automated email is sent correctly to CORE Team members and supervisors on January 20, 2025.

CORE Team Member Initiation of Recommitment Process

Objective: Verify that CORE Team members can successfully initiate and complete their recommitment process.

Supervisor Approval/Decline Functionality

Objective: Validate that supervisors can approve or decline their employee’s recommitment request and provide a reason if declining.

Email Notification for Inaction

Objective: Ensure that the following automated reminder email is sent out to CORE Team members and supervisors on January 27, February 3, 10, 17, and 21 only if there is a pending action from their end.

CORE Team Member Profile Update

Objective: Verify that CORE Team members can update their personal information and availability for deployment.

Tracking and Reporting of Recommitment Status

Objective: Validate that the system tracks each CORE Team member’s recommitment status accurately and that coordinators and supervisors can easily view the recommitment decision.

Testing Tools and Environment:

• Use appropriate testing tools.

• Testing will be conducted in a controlled environment that replicates the production environment as closely as possible.

Test Sign-Off:

• Quality Assurance (QA) will provide test results, identified issues, and recommendations for further improvements. QA will sign-off tickets and hand off to Product Owner (PO) for review.