Skip to content

Test Plan: User Self-Service Profile

Version Date Author Change Description
1.0 2025-09-11 Senior QA Lead Initial Draft with password management.
2.0 2025-09-11 Senior QA Lead Revised for Google SSO; removed all password functionality.

1.0 Introduction

This document outlines the testing strategy for Feature 03: User Self-Service Profile. This feature empowers logged-in users to view their own profile information and update certain personal details. With the integration of Google SSO, password management is no longer part of this feature.

This plan is based on the v2.0 requirements defined in:
- docs/features/03-user-self-service-profile/index.md (BRD)
- docs/features/03-user-self-service-profile/use_case.md (Use Cases)

2.0 Scope

2.1 In Scope

  • Viewing all personal profile data (e.g., email, display name, assigned roles).
  • Verifying that key identifiers like email address and assigned roles are read-only.
  • Editing and successfully saving mutable profile information (e.g., Display Name).
  • Client-side validation for editable fields.

2.2 Out of Scope

  • Changing or resetting the user's password (now managed by Google).
  • Administrators editing a user's profile (covered in Feature 07).
  • Changing a user's primary email, status, or assigned roles/permissions.

3.0 Test Strategy & Approach

  • Functional Testing: Manual tests will be performed to ensure all use cases, including happy paths and error conditions for profile editing, are working as expected.
  • UI/UX Testing: Checks will be performed to ensure the profile page is laid out clearly and that validation messages are user-friendly.
  • Test Environments: QA, Staging.
  • Test Data: One standard, active test user account (standard_user@example.com) is required.

4.0 Test Environment Requirements

  • Backend Service: The AuthService must be deployed and running to handle profile data retrieval and updates.
  • Frontend Application: The web-based enterprise console must be deployed with the User Profile feature fully implemented.
  • Supported Browsers: Google Chrome, Mozilla Firefox, Microsoft Edge (latest stable versions).
  • Database: The test database must contain a fully populated profile for the test user account.

5.0 Test Cases

5.1 Profile Viewing and Editing

Test Case ID User Story Description Steps Expected Result
TC-PROF-001 US-06 Happy Path: View profile information. 1. Log in as standard_user@example.com.
2. Navigate to the "My Profile" page.
3. Observe the displayed information.		 The user's profile information (email, display name, assigned roles) is displayed accurately. The email and roles fields are read-only and cannot be edited.
TC-PROF-002 US-06 Happy Path: Edit and save profile information. 1. Navigate to the "My Profile" page.
2. Click "Edit".
3. Change the "Display Name" to a new value.
4. Click "Save".		 A success message is displayed. The page reflects the updated "Display Name". The name in the application header/shell also updates to the new display name.
TC-PROF-003 US-06 Negative: Attempt to save with invalid data. 1. Navigate to the "My Profile" page.
2. Click "Edit".
3. Clear the "Display Name" field, leaving it empty.
4. Click "Save".		 A validation error message appears (e.g., "Display Name cannot be empty"). The changes are not saved.
TC-PROF-004 US-06 Functional: Cancel an edit operation. 1. Navigate to the "My Profile" page.
2. Click "Edit".
3. Change the "Display Name".
4. Click "Cancel" instead of "Save".		 The changes are discarded. The "Display Name" reverts to its original value.

6.0 UAT Scenarios

Scenario ID User Story Scenario Description Acceptance Criteria
UAT-PROF-01 US-06 A user needs to check their own account details. When I go to my profile page, I can see my correct email, name, and role, and I can't change my email or role.
UAT-PROF-02 US-06 A user wants to update their display name. I can edit my profile, change my display name, and save it. After saving, I see my new name on the screen.

7.0 Entry & Exit Criteria

7.1 Entry Criteria

  • All development for Features 01, 02, and 03 is complete and deployed to the QA environment.
  • All related unit tests are passing.
  • The QA environment is stable and the test user account is configured.

7.2 Exit Criteria

  • All test cases in this plan have been executed.
  • 100% of Critical and High severity defects are closed.
  • UAT has been successfully completed and signed off by stakeholders.