Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Test Plan for Talent Cloud App MVP

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.

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.

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.

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.

  • No labels