Ready for Robotic Testing?

Ready to try robotic testing for CodeBot? Below are a list of standard scenarios the bot can accommodate for.

Prior to robotics training, please complete this intake form and book a meeting with the team for an initial discussion call.

Please also review the scenarios before to determine if the bot testing is aligned with your current processes.

Current Modules:

Recruiting Management (RCM)
Onboarding 2.0 (ONB)
Employee Central (EC)
- ESS/MSS/HRSS Testing
- Time Off requests
- Position Management
Role Based Permissions (RBP)
- Covers None/View/Edit permissions. Field level would be covered by EC testing for field level changes.
- The Bot can identify if the permission requested is what was identified i.e. if checking View, but the Edit pencil is visible, it will flag this in the completed workbook after testing (shows as red).

RCM & ONB Overview

Items in grey are not supported via robotic testing currently.

Test Scenarios currently supported:

Note: Initiate Onboarding is triggered from the Recruiting side, all of the follow‑on steps actually run in Onboarding, so we classify it as an ONB test case.
In the test RCM-04, ensure that you've identified the correct correct pipeline status for this trigger. As long as the required fields—like offer details and start date—are completed, the bot can initiate and move from RCM into ONB.

EC Testing Specifics:

The bot operates by securely proxying as designated users to execute ESS, MSS, and HR processes, ensuring each action reflects the customer’s unique configuration.

The examples below are meant to demonstrate the wide variety of testing that the bot can complete.

Please note that workflows being triggered are not considered part of the bot success - workflows depend on your configuration and data provided to the bot to input. Success is determined by the data being saved.

Test	Scenario	Data needed	Success Criteria
PM/RCM-01	Create Requisition from Position	Position number (consider if there are location-based/other requirements that must be tested in ONB) Any data required for the req that is NOT populated from the position	Requisition created from EC and fully approved into RCM
RCM-02	Create Requisition in RCM	All data points Req Template	Requisition/s created
RCM-02A	Copy existing requisition in RCM	Req Number Number of copies (max 20)	Requisition/s created
RCM-03	Create Candidate Profile	Profile data; External candidates only	Candidate successfully created
RCM-04	Candidate application	Req ID for application Application-specific data Pipeline status (if candidate should be moved through pipeline)	Candidate applied for the job & is in new status; Candidate moved through the relevant pipeline status
RCM-04A	Existing Candidate - apply to new req	Existing candidate profile identifiers (name & email); External candidates only	Existing candidate identified, applied to new req, and placed in the correct status
RCM/ONB-05	Initiate Onboarding	Candidate needs to be IN the right RCM pipeline status and have all relevant integration data filled in (i.e. offer approvals, start dates etc).	Candidate is initiated successfully
ONB-01	Add Candidate to Onboarding (manual)	Position number for hire (if relevant for your environment)	Candidate data created & appears within Onboarding dashboard with completed NHDR.
ONB-02	New Hire Data Review (NHDR)	Confirm candidate is showing in Onboarding dashboard	Data entered in NHDR and submitted.
ONB-03	Candidate Review	Generated data via CodeBot or dummy data entered by company tester for required fields at minimum.	Candidate data collection step is completed successfully.
ONB-04	Assign Tasks (Standard only)	None required in preparation.	Candidate tasks are completed successfully.
ONB-05	Additional Data Collection	None required in preparation.	Additional Data collection is completed successfully.
ONB-06	E-Form Signing	None required in preparation.	All forms are e-signed by candidate and process finalised.
EC - Employee Self Service	Updates to: Personal Information; Contact Information; Emergency Contacts; Home Address	Employee Username; Data being changed i.e. first or last name; Gender; Middle name	Information saved or workflow triggered. If a workflow is triggered, the bot will complete the approvals.
EC - Manager Self Service	Updates to: Any personal data portlets they have access to; Job Information; Compensation Information	Employee Username; Portlet specific information — consider your configuration and rules i.e. if you want to trigger a promotion, data specific to your rule logic needs to be entered to achieve this	Information saved or workflow triggered. If a workflow is triggered, the bot will complete the approvals.
EC - HR Actions	Updates to: Any personal data portlets they have access to; Job Information; Compensation Information	Employee Username; Portlet specific information — consider your configuration and rules i.e. if you want to trigger a promotion, data specific to your rule logic needs to be entered to achieve this	Information saved or workflow triggered. If a workflow is triggered, the bot will complete the approvals.
Time Off	Enter a time off request	Employee Name & Username	Time entry successfully created
PM-01	Position Creation - New	All data points Any customer specific data that is required to trigger workflows	Position created – bot should provide the position number created.
PM-01A	Position Creation – Copy Existing	Copy Existing (no workflow) Position to be copied # of positions Set to be hired = yes/no	Position/s created.
PM-01B	Position Creation – Add Peer/Same & Add Lower Level	Position to be copied Effective date Any other data (customer specific) Any customer specific data that is required to trigger workflows	Position created – bot should provide the position number created.
PM-02	Position - Update Existing or Reactivate	Position number Effective Date Fields to be updated	Ability for the bot to update an existing position i.e. making the To Be Hired field or to change status

Updated on: 02/10/2026

Was this article helpful?

Thank you!