Testing & User Acceptance Testing (UAT)

Once configuration is completed by WSS, BPM manages and validates testing activities through structured UAT procedures. During this phase, BPM partners with Workday Support Services (WSS), functional testers, and stakeholders to ensure all functionality, routing, and data integrity meet business and compliance requirements.

This phase begins once WSS has implemented the approved configuration in a non-production tenant (e.g., UASYS1 or UASYS5) and continues through testing, validation, and formal sign-off.

Purpose

The purpose of this article is to define BPM’s internal testing workflow, tester communication, and the UAT documentation process prior to deployment approval.

Configuration Validation

After WSS completes configuration in UASYS1/UASYS5, BPM verifies the setup:

  • Check routing, conditional rules, and security access.
  • Confirm test data validity.
  • Validate the configuration aligns with approved documentation.

Tester Notifications via TDX

When Jira status updates to Testing, BPM must:

  • Update the TDX ticket with test tenant details.
  • Send TDX notification templates to the requestor and testers.
  • Monitor responses and testing progress.

If testers are unavailable, BPM reassigns testers and reissues notifications.

UAT Framework and Articles

All UAT materials are available under the User Acceptance Testing (UAT) Category.

Article Title Description Link
Getting Started: UAT and Working Group Creation Guidelines for managing Teams groups and UAT communication. View Article
UAT Roles and Responsibilities Defines participant roles and expectations. View Article
User Acceptance Testing Plan Structure for planning, testing, and sign-off. View Article
Creating Effective Testing Scenarios Steps for creating structured, realistic test cases. View Article
UAT Exit Criteria Requirements for final testing approval. View Article
UAT Exit Criteria Template Structured evaluation table for exit readiness. View Article

Defect Tracking and Resolution

Testers document issues in the Testing Tracker (Excel). BPM validates and logs confirmed defects in Jira, tracking status until closure.

Each defect must include:

  • Description and replication steps
  • Severity rating (Critical, Major, Minor)
  • Fix confirmation evidence

Outputs

  • Completed UAT cycle and documentation
  • Resolved Jira defects and test evidence
  • UAT Exit Criteria approval
Print Article