Test Benefits Connectors
Overview
This chapter details how to test benefits end-to-end connectors, including testing procedure and common CCB test scenarios.
Objectives
By the end of this chapter, you will be able to:
- Validate the CCB using the debug service and test mode.
- Validate the output file format and content.
- Test the CCB with benefits scenarios.
Testing Process
Testing your CCB is the most important part of the process. Generally, testing has three cycles:
Cycle | Definition |
|---|---|
Connectivity Testing | Deliver a file to or retrieve a file from the endpoint. |
File Format Testing | Generate an output file populated with the correct data in the correct format. Common issues include:
Functional data problems may cause these issues, in addition to problems with the CCB. Use reports to determine if the correct data is in Workday, and if the integration system reports the data correctly. |
Data and Events Testing | Create test scenarios, like life events, in the tenant. Additionally, check if the integration output file reports the events correctly. |
Clone
If you want to iterate on an integration system, but preserve its current configuration, you can clone it. Cloning creates an entirely separate integration system configured exactly like the original.
To clone an integration system, from its Related Actions, select Integration System, then Clone.
Change Template
If while testing, you determine that your integration system does not use the correct template, you can change it. When you change an end-to-end connector's template, you must reconfigure any integration services, attributes, maps, and field overrides that did not exactly match those on the previous template.
Tip
: To ensure you do not lose the previous configuration, clone your end-to-end connector before changing its template. Then, compare the services, attributes, maps, and field overrides.To change an end-to-end connector's integration template, from its Related Actions, select Integration System, then Change Integration Template.
Debug Service
The Debug Service, available on most CCB templates, enables you to include and exclude specific workers and dependents from the integration. The service provides three launch parameters:
- Exclude Members/Only Include Members: Indicate whether the integration should exclude or include the listed workers and dependents.
- Employees: List the included or excluded members.
- Mask Workday Support Files: Masks sensitive data in case you need to send a file to Workday Support.
Using the Debug Service, you can configure a test scenario for one worker, then easily run the integration and validate the data. Instead of parsing through hundreds of subscribers, you retrieve the specific information you need.
CCB Test Scenarios
To effectively test CCBs, consider which events and data changes in Workday would impact data in the integration file. Some common testing scenarios are:
- Open enrollment
- Termination
- New hire
- Overage dependent
- Job transfer
- International assignment
- Beneficiary change
- Enrollment event rule changes