Skip to main content

Wrkbelt Scheduler Tool - User Acceptance Testing Plan (v0.0.1)

1. Goals of UAT Testing​

The primary goals of User Acceptance Testing for the Wrkbelt Scheduler Tool are to:

  • Validate that the scheduler tool meets the business requirements and user expectations
  • Ensure the booking workflow functions correctly for both existing and new users
  • Identify any usability issues or friction points in the user journey
  • Confirm the system handles edge cases and error scenarios appropriately
  • Gather feedback from stakeholders before the official release

2. UAT Participants​

The following stakeholders will participate in the UAT process:

  • Volodymyr Momot
  • Sean Marx
  • Spencer Marx
  • María Marx
  • Ross Tanchak
  • Olexandra Imereli

3. UAT Scope​

Critical User Flows​

The UAT will focus on validating the following key user flows:

3.1. Existing User Appointment Creation​

  • Confirm users can select available time slots
  • Verify that existing users can retrieve their existing customer information successfully
  • Ensure users can input all required appointment information
  • Validate that appointment confirmation is received
  • Check that appointment details are correctly stored in the system
  • Verify the appointment appears in ServiceTitan

3.2. New User Appointment Creation​

  • Ensure users can select available time slots
  • Confirm new users can complete registration during the booking process
  • Verify all required user information is collected
  • Validate that appointment confirmation is received
  • Check that user account and appointment details are correctly stored
  • Verify the appointment appears in ServiceTitan

3.3 System Under Test​

https://acmeheatingandcooling.co/

4. Test Environment​

4.1. Environment Setup Requirements​

  • Staging Environment: A dedicated staging environment must be fully configured and operational
  • WordPress Integration: WordPress site with the Wrkbelt scheduler tool installed and configured
  • ServiceTitan Connection: Scheduler tool properly connected to ServiceTitan test/staging account
  • Test Data: Sample customer profiles and service configurations available in the system

4.2. Environment Access​

All UAT participants will be provided with:

  • Access credentials for the staging environment
  • Test accounts with appropriate permission levels
  • Documentation for navigating the test environment

5. UAT Assets​

5.1. UAT Checklist​

Google Sheet Link

5.2. Bug Reporting Instructions​

  1. Bug Tracking Tool: All bugs should be reported in Jira
  2. Labeling: Use the label UAT_v0.0.1 for all issues found during testing
  3. Priority Levels:
    • Critical: Blocking issue preventing core functionality
    • High: Major feature not working as expected
    • Medium: Feature works but has significant issues
    • Low: Minor issues, cosmetic problems
  4. Required Information:
    • Clear description of the issue
    • Steps to reproduce
    • Expected vs. actual results
    • Environment details (browser, device)
    • Screenshots or recordings when applicable

5.3. Each tester is responsible for:​

  • Executing assigned test cases on their designated platform
  • Reporting any platform-specific issues following the bug reporting guidelines
  • Verifying responsive design and usability on their platform
  • Providing feedback on platform-specific user experience

5.4. UAT Timeline​

  • UAT Period: May 07-08, 2025

6. Success Criteria​

UAT will be considered successful when:

  1. All participants have completed the test cases in the UAT checklist
  2. No critical or high-priority bugs remain unresolved
  3. All participants agree that the system is ready for production use
  4. All participants have provided feedback on the system

7. Post-UAT Activities​

  1. Compilation of UAT results and feedback
  2. Resolution of identified issues based on priority
  3. Final verification of fixed issues
  4. Preparation for production deployment