Boon Employer Launch Guide

Explore

ATS & HRIS Integration Guides

ATS Integration Testing

Overview

The test plan outlines various scenarios to ensure successful integration between Boon and an ATS. The plan includes checks for immediate data transmission from Boon to ATS and scheduled daily syncs from ATS to Boon. Tests cover authorization of the Boon integration, mapping application stages, job synchronization, including creation and archiving of jobs, and application addition through both ATS job posting URLs and Boon's application flow. Additionally, the plan checks for correct reflection of application status changes and the “Hired” status in Boon.

⁠

Test Scenarios

Sync Frequencies

Some scenarios require a resync to be able to see the reflected changes, this can take up to 24hrs. Please work with Boon team to trigger a forced resync and make this shorter in the testing phase.

Sending data from Boon to the ATS is immediate

Syncing data from the ATS to Boon is scheduled every 24hrs

The sync frequency is not configurable

1. Connecting to the ATS

Scenario: Authorizing Boon Integration via ATS Details Page

Objective: Ensure that the Boon integration can be successfully authorized through the ATS details page, and that Boon reflects the integration status as “Authorized.”

Steps:

1. Navigate to the Integration section within the Boon Admin App.

2. Select the specific ATS you want to integrate with, which will take you to the ATS details page.

3. On the ATS details page, locate and click the “Authorize Boon” button.

4. Follow the prompts provided to complete the authorization process. This may involve logging into the ATS, granting permissions, and confirming the connection.

5. Once the process is complete, return to the Boon Admin App.

6. Verify that the status on the integration details page in Boon changes to “Authorized.”

Expected Result: After following the authorization steps, Boon should display the status as “Authorized” on the ATS details page, indicating a successful integration.

Scenario 1.2: Application Stages Mapping with Boon Tracker Stages

Objective: Ensure that the application stages in the ATS are correctly mapped to Boon Tracker stages, particularly for “Applied” and “Hired,” and that all stages appear in the correct order.

Steps:

1. Go to the integration section in Boon Admin App and verify the mapping for “Applied” and “Hired” stages between the ATS and Boon Tracker.

2. After ensuring the correct mapping, visit the Tracker section in the Admin App.

3. Verify that all stages from the ATS are displayed in Boon Tracker,

4. Verify that all stages are displayed in the correct order.

Expected Result: All stages from the ATS should be visible in Boon Tracker, correctly mapped and ordered, with special attention to “Applied” and “Hired” stages.

⁠

2. Job Synchronization

Scenario 2.1: Adding a Job in ATS

Objective: Ensure that when a job is created in the ATS, it is correctly synced and appears in Boon.

Steps:

1. Create a new job in the ATS with the following fields: title, description, location, and any other relevant details.

2. Perform a sync operation between the ATS and Boon.

3. Verify that the job appears in Boon with the correct title, description, location, and any reward templates (if reward automation is enabled).

Expected Result: The job created in the ATS should appear in Boon with all fields correctly mapped, including any automated reward templates.

Scenario 2.2: Archiving or Marking a Job as Filled in ATS

Objective: Ensure that when a job is archived or marked as filled in the ATS, this status is reflected in Boon.

Steps:

1. Archive or mark a job as filled in the ATS.

2. Perform a sync operation between the ATS and Boon.

3. Verify that the job status in Boon is updated to reflect the archived or filled status.

Expected Result: The job should either be removed from the active listings in Boon or marked appropriately as filled.

⁠

3. Adding Applications

Scenario 3.1: Adding application using Job Posting URL

Note: this only applies in case the ATS supports syncing Job Posting URLs and the job synced has this a Job Posting URL

Objective: Ensure that when a referral is sent to a candidate, they are redirected to the ATS job posting URL, and their application status is tracked in Boon.

Steps:

1. Send a referral to a candidate for a job that has a posting URL in the ATS.

2. The candidate clicks the link in Boon and is redirected to the ATS job posting page.

3. The candidate completes the application in the ATS.

4. Perform a sync operation between the ATS and Boon.

5. Verify that the application is shown in Boon tracker.

Expected Result: The candidate should be redirected to the ATS job posting page, and their application should be visible in Boon after syncing.

Scenario 3.2: Adding application using Boon Application flow

Note: this applies when the job has no external Job posting URL

Objective: Ensure that when a referral is sent to a candidate, Boon’s application flow is triggered, and the application is correctly sent to the ATS.

Steps:

1. Send a referral to a candidate for a job that does not have a posting URL or is not supported by the ATS.

2. The candidate clicks the link in Boon and is redirected to Boon’s application flow.

3. The candidate completes the application on Boon.

4. Verify that the application is sent to the ATS immediately with :

Candidate name and email

Candidate resume is attached

Application/Candidate source is marked as BOON

Expected Result: The application should be successfully submitted to the ATS with the correct info

⁠

4. Tracking Applications

Scenario 4.1: Application Status Changes in ATS

Objective: Ensure that when an application’s status is updated in the ATS, this change is reflected in Boon.

Steps:

1. Update the status of a candidate’s application in the ATS (e.g., move from “Applied” to “Interviewing”).

2. Perform a sync operation between the ATS and Boon.

3. Verify that the updated application status is reflected in Boon Tracker

Expected Result: The application status in Boon should mirror the status in the ATS.

Scenario 4.2: Candidate Reaches Hired Status in ATS

Objective: Ensure that when a candidate’s application status reaches “Hired” in the ATS, this is correctly reflected in Boon.

Steps:

1. Change the candidate’s application status to “Hired” in the ATS.

2. Perform a sync operation between the ATS and Boon.

3. Verify that Boon reflects the “Hired” status for the candidate’s application.

Expected Result: The candidate’s status should be updated to “Hired” in Boon, signaling a successful placement.

Scenario 4.3: Application Rejection Handling and Archival in Boon

Objective: Ensure that when an application is rejected in the ATS, it is correctly reflected as “Archived” in Boon, along with the accurate rejection reason assigned.

Steps:

1. In the ATS, locate an active candidate application.

2. Change the application status to “Rejected” and assign a specific rejection reason (e.g., “Not a Fit,” “Incomplete Application,” etc.).

3. Perform a sync operation between the ATS and Boon.

4. After the sync is complete, navigate to Boon and check the candidate’s profile in the tracker.

5. Verify that:

⁠

The application is marked as “Archived” in Boon.

⁠

The correct rejection reason assigned in the ATS is accurately displayed in Boon.

Overview

Test Scenarios

Sync Frequencies

1. Connecting to the ATS

Scenario: Authorizing Boon Integration via ATS Details Page

Scenario 1.2: Application Stages Mapping with Boon Tracker Stages

2. Job Synchronization

Scenario 2.1: Adding a Job in ATS

Scenario 2.2: Archiving or Marking a Job as Filled in ATS

3. Adding Applications

Scenario 3.1: Adding application using Job Posting URL

Scenario 3.2: Adding application using Boon Application flow

4. Tracking Applications

Scenario 4.1: Application Status Changes in ATS

Scenario 4.2: Candidate Reaches Hired Status in ATS

Scenario 4.3: Application Rejection Handling and Archival in Boon

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.