Catapult Application - User Acceptance Test (UAT) Plan
1. UAT Plan & Schedule
1.1 Objectives
- Verify Catapult meets all business, user, and technical requirements for Catalog, Profile, and Learn modules.
- Ensure all user roles (Officer, Supervisor, Mentor, CDO, Admin, Superuser) can perform their expected tasks.
- Validate integration with Joomla and adherence to UI/UX, accessibility, and security standards.
1.2 Scope
- All high-level, detailed, and technical requirements as listed in the requirements section.
- All user roles and their permissions.
- End-to-end workflows for Catalog, Profile, and Learn.
1.3 Team & Roles
- UAT Lead: Coordinates UAT, tracks progress, and reports results.
- Business Users: Officers, Supervisors, Mentors, CDOs.
- Admin/Superuser: Test admin-specific features.
- Support: Developers and QA for defect triage.
1.4 Schedule
| Phase | Dates | Responsible |
|---|---|---|
| UAT Planning | June 12 | UAT Lead |
| Test Data Setup | June 13 | Admin/Support |
| UAT Execution | June 14–18 | All Testers |
| Defect Resolution | June 19–20 | Dev/QA |
| Retest/Regression | June 21 | All Testers |
| UAT Sign-off | June 22 | UAT Lead/Stakeholder |
2. UAT Test Case Template
Test Case ID:
Requirement:
User Role:
Preconditions:
Test Steps:
Pass/Fail:
Comments/Defects:
Requirement:
User Role:
Preconditions:
Test Steps:
Pass/Fail:
Comments/Defects:
3. UAT Test Execution Log Template
| Date | Tester | Test Case ID | Pass/Fail | Comments/Defects |
|---|---|---|---|---|
4. UAT Summary Report Template
| Metric | Value |
|---|---|
| Total Test Cases | |
| Passed | |
| Failed | |
| Blocked | |
| Defects Raised | |
| Defects Resolved | |
| UAT Sign-off Status | |
| Comments |
5. Detailed UAT Test Cases & Scripts
5.1 Catalog
CAT-01: Browse Courses
- User Role: Officer, Supervisor, Mentor, CDO, Admin, Superuser
- Preconditions: User is logged in with appropriate role.
- Test Steps:
- Navigate to the Catalog section.
- Verify a list of courses is displayed with title, category, sub-category, modality, and proficiency.
- Click a course to view its details.
- Expected Result: Courses and details are displayed correctly.
CAT-02: Categorization & Tagging
- User Role: All roles (view), Admin/Superuser (manage)
- Preconditions: Categories and tags exist.
- Test Steps:
- As Admin, create/edit/delete categories and tags.
- Assign categories/tags to courses.
- As Officer, filter courses by category/tag.
- Expected Result: Categories/tags are managed and filterable.
CAT-03: Search & Filter
- User Role: All roles
- Preconditions: Courses exist in the catalog.
- Test Steps:
- Use the search bar to find a course by keyword.
- Apply filters for category, sub-category, proficiency, and modality.
- Observe the total number of courses displayed.
- Expected Result: Search and filters work as expected. The course count updates accordingly.
CAT-04: Course Registration (Internal/External)
- User Role: All roles
- Preconditions: Courses with both internal and external registration exist.
- Test Steps:
- Open a course detail page.
- For internal courses, click the registration link.
- For external courses, verify the registration URL is displayed and can be copied.
- Expected Result: Registration works as expected for both types.
CAT-05: Add to Learning Plan
- User Role: Officer, Supervisor, Mentor, CDO
- Preconditions: User is logged in and viewing a course detail.
- Test Steps:
- Click "Add to Learning Plan" on a course detail page.
- Navigate to the user's learning plan and verify the course is listed.
- Expected Result: Course appears in the learning plan.
CAT-06: Admin Catalog Management
- User Role: Admin, Superuser
- Preconditions: Admin access to catalog management.
- Test Steps:
- Create, update, delete, and hide courses, categories, subcategories, proficiency levels, and modalities.
- Verify changes as a regular user.
- Expected Result: Catalog updates are reflected for all users.
CAT-07: Data Import/Export
- User Role: Admin, Superuser
- Preconditions: Access to ETL/data management.
- Test Steps:
- Import catalog data from JSON, XML, or CSV.
- Export catalog data to each format.
- Verify catalog updates accordingly.
- Expected Result: Data import/export works as expected.
CAT-08: Course Feedback & Questions
- User Role: All roles
- Preconditions: Feedback/question form is available.
- Test Steps:
- Submit feedback or a question for a course.
- Verify submission is received by the appropriate mail group.
- Expected Result: Feedback/question is sent and acknowledged.
5.2 Profile
PRO-01: Create/Update Profile
- User Role: Officer, Admin, Superuser
- Preconditions: User is logged in.
- Test Steps:
- Navigate to Profile section.
- Create or update profile information.
- Save and verify changes.
- Expected Result: Profile is created or updated successfully.
PRO-02: Define Relationships
- User Role: Officer, Admin, Superuser
- Preconditions: User is logged in.
- Test Steps:
- Edit profile to add Mentor, CDO, and Supervisor.
- Save and verify relationships are displayed.
- Expected Result: Relationships are saved and visible.
PRO-03: Experience Validation
- User Role: Officer, Supervisor, Admin, Superuser
- Preconditions: User has added experience to profile.
- Test Steps:
- Officer adds education and work experience.
- Supervisor reviews and validates experience.
- Officer verifies validation status.
- Expected Result: Experience is validated and status is updated.
PRO-04: Career Acceleration
- User Role: Supervisor
- Preconditions: Officer profile exists.
- Test Steps:
- Supervisor flags an Officer for fast-tracking.
- Officer and Admin verify status update.
- Expected Result: Officer is flagged for career acceleration.
PRO-05: Profile Deletion Request
- User Role: Officer
- Preconditions: Officer profile exists.
- Test Steps:
- Officer requests profile deletion.
- Admin reviews and processes the request.
- Officer verifies profile status.
- Expected Result: Deletion workflow is triggered and processed.
5.3 Learn
LEA-01: Learning Tracks
- User Role: Officer, Admin, Superuser
- Preconditions: Learning tracks exist.
- Test Steps:
- View available learning tracks.
- Enroll in a track.
- Verify courses are added to learning plan.
- Expected Result: Track enrollment works and courses are added.
LEA-02: Request Workflow
- User Role: Officer, Supervisor
- Preconditions: Officer is enrolled in a course requiring approval.
- Test Steps:
- Officer requests training.
- Supervisor approves or denies the request.
- Officer verifies request status.
- Expected Result: Request workflow functions as expected.
LEA-03: Course Schedule
- User Role: Officer
- Preconditions: Officer has courses in learning plan.
- Test Steps:
- Add upcoming course dates and completion dates.
- Mark courses as completed.
- Verify schedule updates.
- Expected Result: Schedule is tracked and updated.
LEA-04: Custom Learning Plans
- User Role: Officer, Admin, Superuser
- Preconditions: User is logged in.
- Test Steps:
- Add custom courses to learning plan (not in catalog).
- Specify course title, source, modality, and proficiency.
- Verify custom course appears in plan.
- Expected Result: Custom learning plan is updated.
5.4 Technical/Access
TEC-01: Access Control
- User Role: All roles
- Preconditions: User accounts exist for each role.
- Test Steps:
- Attempt to access the application without logging in.
- Log in as each role and verify access to permitted features only.
- Expected Result: Access is restricted by role and login status.
TEC-02: UI Consistency & Accessibility
- User Role: All roles
- Preconditions: Application is running in a browser.
- Test Steps:
- Inspect headings, lists, and forms for consistent styling.
- Test keyboard navigation and screen reader compatibility.
- Resize window to test responsive design.
- Expected Result: UI matches design, is accessible, and responsive.