Oracle Fusion Candidate Screening Test Cases
Validate screening question responses, automated disposition, candidate ranking and recruiter shortlisting decisions across Oracle Fusion HCM Recruiting — a comprehensive catalog of 22 individual Candidate Screening test scenarios spanning screening questions, automated disposition, ranking/shortlisting and negative/security screening testing — all using masked, synthetic candidate data.
| Test ID | ORCL.HCM.RECRUIT.SCREEN |
| Application | Oracle Fusion Cloud |
| Product | HCM |
| Module | Recruiting |
| Process | Candidate Screening |
| Business Flow | Recruit-to-Hire |
| Scenario Type | Positive / Negative / Security |
| Test Usage | Functional Testing / Regression Testing / UAT Sign-Off |
| Priority | High |
| Automation | SyntraFlow Ready |
| Library | Syntra Standard |
Note on test design: SyntraFlow executes the detailed Oracle Fusion HCM Recruiting UI interactions automatically while presenting the scenario as business-readable test steps for documentation, review and reporting. This scenario is presented as 7 business-readable test steps; SyntraFlow's automation executes approximately 24 underlying Oracle Fusion UI actions to complete it.
Test Objective
This test validates screening question responses, automated disposition, candidate ranking and recruiter shortlisting decisions across Oracle Fusion HCM Recruiting, using only masked or synthetic candidate data.
The scenario should confirm that:
- each screening question response entered for ${CANDIDATE} against ${REQUISITION} is correctly captured and scored
- knockout and disqualifying screening questions correctly disqualify ineligible candidates rather than allowing them to progress
- auto-disposition is correctly applied based on the configured ${SCREENING_SCORE} rule, and manual recruiter screening is correctly recorded
- candidates are correctly ranked and shortlisted according to ${SCREENING_SCORE} and ${RANKING_CRITERIA}
- deliberately invalid entries — missing required answers, invalid question configuration, scoring errors, duplicate submissions — are correctly rejected or flagged rather than silently accepted
- unauthorized users cannot view candidate screening results without the required security access
A negative or security Candidate Screening scenario passes when Oracle correctly enforces the expected data, eligibility or security rule; this test does not attempt to certify a specific Oracle application defect. Where an entry or validation appears unexpected or its cause is unclear, it is treated as requiring further investigation and supporting evidence rather than a confirmed conclusion. This page catalogs 22 individual Candidate Screening scenarios as a single comprehensive reference rather than as separate indexable pages, and uses only masked or synthetic candidate data throughout.
When to Use This Test
- Functional testing of candidate screening for a new Oracle Fusion HCM Recruiting implementation
- Regression testing of screening questions, disposition and ranking after an Oracle quarterly update affecting Recruiting
- UAT sign-off for candidate screening across screening-question, disposition, ranking/shortlisting and negative/security scenarios
- Baseline screening coverage referenced by Interview and Job Offer within the same Recruiting cluster
- Comprehensive scenario coverage for teams standardizing on a single Candidate Screening regression pack instead of dozens of near-duplicate scripts
Where This Test Fits in the Recruit-to-Hire Process
Candidate Screening is the third scenario family in the Recruiting cluster. It exercises screening-question, disposition and ranking/shortlisting coverage, together with negative and security validation, and feeds Interview and Job Offer downstream. Exact screening question configuration, scoring weights and disposition rules depend on requisition template, questionnaire setup and customer-specific Oracle Fusion configuration.
Preconditions
- Oracle Fusion Recruiting access is available to the test user.
- An open ${REQUISITION} with an active candidate pipeline exists.
- A representative synthetic ${CANDIDATE} with submitted screening question responses exists for the requisition.
- Configured ${SCREENING_QUESTION} items, including at least one knockout and one weighted-scoring question, are available.
- A ${RECRUITER} with screening and disposition authorization is available for the requisition.
- At least one ${TALENT_POOL} is configured for candidates not selected for the current requisition.
- A user without screening-results authorization is available for security testing.
Exact screening question configuration, scoring weights and disposition rules may vary by Oracle Fusion implementation, requisition template and customer-specific configuration.
Sample Test Data
| Candidate | ${CANDIDATE} |
| Requisition | ${REQUISITION} |
| Screening Question | ${SCREENING_QUESTION} |
| Screening Score | ${SCREENING_SCORE} |
| Disposition Reason | ${DISPOSITION_REASON} |
| Recruiter | ${RECRUITER} |
| Talent Pool | ${TALENT_POOL} |
| Ranking Criteria | ${RANKING_CRITERIA} |
Sample values are illustrative ${PLACEHOLDER} tokens, not real candidate, requisition or recruiter data. Replace them with masked or synthetic candidate data from the target Oracle Fusion TEST or UAT environment; not every field applies to every scenario.
Test Steps
7 business-readable steps. SyntraFlow's automation executes ~24 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.
| # | User Action | Expected Result |
|---|---|---|
| 1 | Sign In to Oracle Fusion HCM Sign in to Oracle Fusion Cloud with a user account that has Recruiting access. | The Oracle Fusion Cloud home page loads successfully for the authenticated user. |
| 2 | Navigate to Candidate Pipeline Navigate to the requisition's candidate pipeline within Oracle Fusion Recruiting. ${REQUISITION} | The candidate pipeline for the requisition opens successfully. |
| 3 | Review Screening Question Responses Open the candidate's application and review the recorded screening question responses. ${CANDIDATE} / ${SCREENING_QUESTION} | The screening question responses are displayed correctly for the candidate. |
| 4 | Verify Calculated Screening ScoreBusiness assertion Verify the screening score calculated from the candidate's screening question responses. ${SCREENING_SCORE} Correctly flagging a scoring or configuration issue is a passing outcome for negative scenarios, not a failure. | The calculated screening score correctly reflects the candidate's responses and configured weighting. |
| 5 | Apply or Confirm Auto-Disposition Apply or confirm the disposition applied to the candidate based on the configured screening rule, or manually screen the candidate. ${DISPOSITION_REASON} / ${RECRUITER} | The disposition is applied or confirmed correctly, or a deliberately invalid disposition attempt is rejected with the expected validation. |
| 6 | Rank and Shortlist Candidates Rank candidates in the pipeline by screening score and shortlist the top-ranked candidates for the requisition. ${SCREENING_SCORE} / ${RANKING_CRITERIA} / ${TALENT_POOL} | Candidates are ranked and shortlisted correctly according to the configured ranking criteria. |
| 7 | Verify Disposition and Ranking Recorded CorrectlyBusiness assertion Confirm that the candidate's disposition, screening score and ranking position recorded correctly against the requisition. This is the main business assertion for the scenario across the full catalog of 22 Candidate Screening variations. | The disposition, score and ranking recorded correctly, and status accurately reflects a valid screening outcome or an expected validation for an invalid one. |
Expected Results
- Each screening question response for the candidate recorded correctly against the requisition.
- Weighted scoring and knockout questions correctly contribute to or disqualify the calculated screening score.
- Auto-disposition and manual recruiter screening decisions recorded correctly with the applied disposition reason.
- Candidate ranking and shortlisting correctly reflect the screening score and ranking criteria.
- Deliberately invalid entries raise the expected data or configuration validation rather than being silently accepted.
- Unauthorized users are correctly prevented from viewing candidate screening results.
Key Validation Checkpoints
- Screening responses correctly captured and scored.
- Auto-disposition correctly applied per configured rules.
- Knockout questions correctly disqualify ineligible candidates.
- Ranking correctly reflects screening scores.
- Recruiter overrides correctly recorded with audit trail.
- Unauthorized access to screening results correctly blocked.
Go Beyond the Standard Test with Jarvis AI
The Syntra Standard Test Library defines the core Candidate Screening scenario. Jarvis AI can extend this scenario by systematically generating additional Positive, Negative and Security variations using customer-specific candidate, requisition and screening-question data available through Syntra DataVault.
Teams do not need to manually construct dozens of near-identical screening scenarios to cover every screening question, disposition rule and ranking combination. Jarvis uses the standard screening scenario as the foundation and generates coverage relevant to the customer's environment — without creating additional indexable pages, and never using real candidate data.
From Standard Test to Executed Regression Pack
Rather than maintaining a separate test for every possible candidate screening condition, SyntraFlow maintains one core Candidate Screening scenario and allows Jarvis AI to generate Positive, Negative and Security variations using the customer's available requisition and screening-question test data — never real candidate data.
AI-Generated Test Variations
The same Candidate Screening business scenario can produce many test variations without creating separate public library pages. Below is a real slice of SyntraFlow's Build Scripts library, filtered to HCM Recruiting.
- Required and knockout screening questions answered correctly
- Weighted scoring screening questions
- Auto-disposition based on the calculated screening score
- Manual recruiter screening and disposition
- Candidate ranking and shortlisting by screening score
- Recruiter override of an auto-disposition
- Missing required screening answer
- Invalid screening question configuration
- Screening score calculation error
- Disposition applied to a withdrawn application
- Duplicate screening submission
- Unauthorized access to candidate screening results
These are representative examples only. Screening question configuration, scoring weights, disposition rules and access controls can depend on the customer's Oracle Fusion configuration and requisition setup — not every Oracle configuration behaves identically.
Generated Using Your DataVault Test Data
Generic test data rarely represents every screening question, scoring weight and disposition rule combination in a real Oracle Fusion HCM Recruiting environment. Where connected, Jarvis can use approved, masked or synthetic test data available through Syntra DataVault — Candidate, Requisition, Screening Question and Screening Score — to construct realistic Candidate Screening variations relevant to the customer's actual implementation, without ever using real candidate data.
Standard Library Definition
Candidate ${CANDIDATE}
Requisition ${REQUISITION}
Screening Question ${SCREENING_QUESTION}
Screening Score ${SCREENING_SCORE}
Disposition Reason ${DISPOSITION_REASON}
Recruiter ${RECRUITER}
Talent Pool ${TALENT_POOL}
Ranking Criteria ${RANKING_CRITERIA}
DataVault
Candidates Synthetic candidate identities with masked screening responses Screening Questions Required, knockout and weighted-scoring questions Disposition Rules Auto-disposition thresholds and manual disposition reasons Talent Pools Configured pools for non-selected candidates Security Roles with and without screening-results authorization
Jarvis AI Generates
Scenario 01 — Candidate Answers Required Screening Questions Scenario 02 — Weighted Scoring Question Scenario 03 — Auto-Disposition Based on Screening Score Scenario 04 — Rank Candidates by Screening Score Scenario 05 — Missing Required Screening Answer Scenario 06 — Unauthorized User Accesses Screening Results ...
Candidate Screening test data can include screening responses, calculated scores and disposition decisions tied to individual candidates. SyntraFlow test scenarios use ${PLACEHOLDER} tokens rather than real candidate names, contact details or responses, and all candidate identities and screening responses used in testing are synthetic or masked via Syntra DataVault. Where DataVault masking and privacy controls are configured, they apply to the underlying customer test data used to generate variations across the Candidate Screening catalog. See /datavault/ and /datavault/data-masking/ for more detail on DataVault privacy and masking controls.
Example Test Variations
A comprehensive catalog of 22 individual Candidate Screening test scenarios spanning screening questions, automated disposition, ranking/shortlisting and negative/security screening testing — all using masked, synthetic candidate data. Filter or search below.
| ID | Variation | Type | Key Difference | Execution |
|---|---|---|---|---|
| REC-SCR-001 | Candidate Answers Required Screening Questions | Positive | Validate that ${CANDIDATE} answers all required ${SCREENING_QUESTION} items for ${REQUISITION}; Oracle records each response against the candidate's application. | SyntraFlow Ready |
| REC-SCR-002 | Candidate Answers Knockout Question | Positive | Validate that ${CANDIDATE}'s response to a configured knockout ${SCREENING_QUESTION} for ${REQUISITION} is correctly captured; Oracle records the response and applies the knockout rule. | SyntraFlow Ready |
| REC-SCR-003 | Screening Question with Weighted Scoring | Positive | Validate that a weighted ${SCREENING_QUESTION} response from ${CANDIDATE} contributes correctly to the calculated ${SCREENING_SCORE} for ${REQUISITION}. | SyntraFlow Ready |
| REC-SCR-004 | Screening Question Triggers Auto-Disqualification | Positive | Validate that ${CANDIDATE}'s response to a disqualifying ${SCREENING_QUESTION} correctly triggers auto-disqualification for ${REQUISITION}; Oracle applies the configured ${DISPOSITION_REASON}. | SyntraFlow Ready |
| REC-SCR-005 | Multiple Screening Questionnaires per Requisition | Positive | Validate that ${CANDIDATE} can complete multiple screening questionnaires configured for ${REQUISITION}; Oracle records responses to each questionnaire correctly. | SyntraFlow Ready |
| REC-SCR-006 | Recruiter Manually Screens Candidate | Positive | Validate that ${RECRUITER} can manually review and screen ${CANDIDATE}'s application for ${REQUISITION}; Oracle records the manual screening decision. | SyntraFlow Ready |
| REC-SCR-007 | Auto-Disposition Based on Screening Score | Positive | Validate that Oracle automatically applies disposition to ${CANDIDATE} based on the calculated ${SCREENING_SCORE} against the configured rule for ${REQUISITION}. | SyntraFlow Ready |
| REC-SCR-008 | Move Candidate to Next Stage | Positive | Validate that ${RECRUITER} moves ${CANDIDATE} to the next pipeline stage for ${REQUISITION} following screening; Oracle records the stage change correctly. | SyntraFlow Ready |
| REC-SCR-009 | Reject Candidate with Disposition Reason | Positive | Validate that ${RECRUITER} rejects ${CANDIDATE} for ${REQUISITION} with a selected ${DISPOSITION_REASON}; Oracle records the rejection and reason correctly. | SyntraFlow Ready |
| REC-SCR-010 | Move Candidate to Talent Pool | Positive | Validate that ${RECRUITER} moves ${CANDIDATE} into ${TALENT_POOL} following screening for ${REQUISITION}; Oracle records the talent pool assignment correctly. | SyntraFlow Ready |
| REC-SCR-011 | Rank Candidates by Screening Score | Positive | Validate that candidates for ${REQUISITION} are ranked according to their calculated ${SCREENING_SCORE}; Oracle displays the ranking in the correct order. | SyntraFlow Ready |
| REC-SCR-012 | Shortlist Top-Ranked Candidates | Positive | Validate that ${RECRUITER} shortlists the top-ranked candidates, including ${CANDIDATE}, for ${REQUISITION} based on ${RANKING_CRITERIA}; Oracle records the shortlist correctly. | SyntraFlow Ready |
| REC-SCR-013 | Compare Candidates Side-by-Side | Positive | Validate that ${RECRUITER} can compare ${CANDIDATE} against other candidates side-by-side for ${REQUISITION} using ${SCREENING_SCORE} and ${RANKING_CRITERIA}. | SyntraFlow Ready |
| REC-SCR-014 | Filter Candidates by Screening Criteria | Positive | Validate that ${RECRUITER} filters the candidate pipeline for ${REQUISITION} using ${RANKING_CRITERIA} and ${SCREENING_SCORE} thresholds; Oracle returns the correctly filtered set. | SyntraFlow Ready |
| REC-SCR-015 | Recruiter Overrides Auto-Disposition | Positive | Validate that ${RECRUITER} overrides the auto-disposition applied to ${CANDIDATE} for ${REQUISITION} with a manual ${DISPOSITION_REASON}; Oracle records the override with an audit trail. | SyntraFlow Ready |
| REC-SCR-016 | Missing Required Screening Answer | Negative | Validate that ${CANDIDATE} submitting an application for ${REQUISITION} with a missing required ${SCREENING_QUESTION} response is rejected; Oracle raises the expected data validation. | SyntraFlow Ready |
| REC-SCR-017 | Invalid Screening Question Configuration | Negative | Validate that an invalidly configured ${SCREENING_QUESTION} on ${REQUISITION} is handled correctly; Oracle raises the expected configuration validation rather than silently accepting it. | SyntraFlow Ready |
| REC-SCR-018 | Screening Score Calculation Error | Negative | Validate that a ${SCREENING_SCORE} calculation error for ${CANDIDATE} on ${REQUISITION} is correctly detected rather than silently producing an incorrect score. | SyntraFlow Ready |
| REC-SCR-019 | Disposition Applied to Withdrawn Application | Negative | Validate that attempting to apply a ${DISPOSITION_REASON} to a withdrawn application from ${CANDIDATE} for ${REQUISITION} is correctly blocked; Oracle raises the expected validation. | SyntraFlow Ready |
| REC-SCR-020 | Duplicate Screening Submission | Negative | Validate that a duplicate screening response submission from ${CANDIDATE} for the same ${SCREENING_QUESTION} on ${REQUISITION} is correctly rejected. | SyntraFlow Ready |
| REC-SCR-021 | Screening Bypassed for Ineligible Candidate | Negative | Validate that an ineligible ${CANDIDATE} cannot bypass required screening for ${REQUISITION}; Oracle raises the expected eligibility validation. | SyntraFlow Ready |
| REC-SCR-022 | Unauthorized User Accesses Screening Results | Negative/Security | Validate that a user without screening-results authorization cannot view ${CANDIDATE}'s screening results or ${SCREENING_SCORE} for ${REQUISITION}; Oracle blocks the unauthorized access. | SyntraFlow Ready |
No variations match this filter.
Positive and Negative Candidate Screening Testing
Positive Testing
Jarvis generates scenarios designed to confirm that Oracle Fusion HCM Recruiting correctly captures screening responses, calculates the screening score and applies disposition and ranking when the candidate, requisition and screening-question data are all valid.
Required Screening Questions Answered + Weighted Scoring → Screening Score Calculated and Disposition Applied Correctly
Negative Testing
Jarvis can also generate scenarios that deliberately violate a data, configuration or security rule to confirm Oracle correctly rejects or flags the condition rather than silently accepting it.
- Missing Required Screening Answer → Expected Data Validation Displayed
- Invalid Screening Question Configuration → Expected Configuration Validation Displayed
- Screening Score Calculation Error → Expected Data Validation Displayed
- Disposition Applied to Withdrawn Application → Expected Validation Displayed
- Duplicate Screening Submission → Expected Data Validation Displayed
- Unauthorized User → Access Prevented
A negative recruiting scenario passes when Oracle correctly enforces the expected data, eligibility or security rule
| Scenario | Oracle Outcome | Test Result |
|---|---|---|
| Valid requisition data | Requisition created | PASS |
| Missing required field | Validation occurs | PASS |
| Headcount exceeds budget | Validation occurs | PASS |
| Unauthorized user | Access prevented | PASS |
| Unexpected application exception | Unexpected failure | FAIL |
Turn AI-Generated Variations into a Regression Pack
Users can select generated Candidate Screening scenarios and group them into reusable execution packs.
HCM Candidate Screening Regression Pack
- Candidate Answers Required Screening Questions
- Candidate Answers Knockout Question
- Screening Question with Weighted Scoring
- Auto-Disposition Based on Screening Score
- Move Candidate to Next Stage
- Rank Candidates by Screening Score
- Shortlist Top-Ranked Candidates
- Missing Required Screening Answer
- Duplicate Screening Submission
- Unauthorized User Accesses Screening Results
Run On-Demand or Schedule Automated Batch Execution
SyntraFlow can execute selected Candidate Screening scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.
Once scheduled, SyntraFlow executes the selected Candidate Screening scenarios unattended and records the outcome of each test and business assertion.
| Pack | HCM Candidate Screening Regression Pack |
| Schedule | Weekly Regression |
| Tests | 22 scenarios |
| Execution | Batch Mode |
| Start | 9:00 PM |
| Environment | Oracle Fusion TEST |
| Status | Scheduled |
Illustrative example — not a live schedule.
Review Results Across the Entire Test Pack
Users can drill from the regression pack into a scenario, its business steps, the underlying automation actions, and the evidence captured for each.
Illustrative example data — not actual production metrics.
Regression Pack → Scenario → Business Step → Automation Action → Evidence
DataVault HCM Persona
Rather than generating variations from disconnected field values, Jarvis can draw on a DataVault persona built for candidate screening — a pre-grouped, internally consistent set of synthetic candidate, requisition and screening-question dimensions, so Jarvis constructs realistic Candidate Screening scenarios rather than combining incompatible or unrepresentative data.
| Candidate | ${CANDIDATE} |
| Requisition | ${REQUISITION} |
| Screening Question | ${SCREENING_QUESTION} |
| Screening Score | ${SCREENING_SCORE} |
| Disposition Reason | ${DISPOSITION_REASON} |
| Recruiter | ${RECRUITER} |
| Talent Pool | ${TALENT_POOL} |
DataVault personas group dependent recruiting dimensions so Jarvis generates coherent, internally consistent Candidate Screening scenarios using only masked or synthetic candidate data, rather than arbitrary and potentially unrepresentative field combinations.
Security & Access Variations
Oracle Fusion HCM Recruiting role and security configuration is customer-specific, so SyntraFlow can exercise candidate screening under different personas to confirm the customer's own access model behaves as expected, rather than assuming a universal Oracle security model.
| Persona | Action | Expected | Syntra Result |
|---|---|---|---|
| Recruiter | View Screening Results for Assigned Requisitions | Allowed | PASS |
| Hiring Manager | View Shortlisted Candidates | Allowed | PASS |
| Unauthorized User | Attempts to View Screening Results | Access prevented | PASS |
Understand Why a Test Failed
SyntraFlow execution evidence can help distinguish business-data failures, configuration issues, automation problems and potential application defects.
From Business Scenario to Execution Evidence
Business teams get readable test documentation; automation teams retain detailed execution traceability.
Meet Jarvis — SyntraFlow's AI Testing Engine
Jarvis extends the Syntra Standard Test Library by analysing the Candidate Screening scenario, available DataVault test data and expected business outcomes to systematically generate Positive, Negative and Security coverage for the customer's environment, using only masked or synthetic candidate data.
How SyntraFlow Automates This Test
The Standard Test defines the scenario; DataVault, Jarvis AI and SyntraFlow's execution engine take it from a single reusable business definition to executed, evidenced regression coverage.
Business Step → Underlying UI Actions
What SyntraFlow Captures Per Run
Action Status vs. Business Validation
A successful UI interaction does not automatically prove a screening response was correctly scored or a disposition correctly applied — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution. Because this page aggregates 22 individual scenarios across screening questions, disposition, ranking/shortlisting and negative/security testing, evidence-based failure classification matters most here. When a step or business assertion fails, SyntraFlow's evidence is intended to help classify the likely cause into one of eight categories — DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, INTEGRATION_ERROR, AUTOMATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — rather than assuming a defect. For example: Auto-disposition did not apply expected screening rule — Likely category: CONFIGURATION_ERROR or DATA_ERROR depending on evidence — Evidence: the disposition rule configuration does not match the screening score threshold, or the underlying screening score was calculated incorrectly — Recommended action: verify the disposition rule configuration and the screening score calculation before resubmitting. A failure should not be labeled as an Oracle application defect until data, configuration, security, automation and integration causes have been eliminated.
| Step | Action Status | Business Validation |
|---|---|---|
| Verify Calculated Screening Score | Pass | — |
| Apply or Confirm Auto-Disposition | Pass | — |
| Verify Disposition and Ranking Recorded Correctly | Pass | Pass |
Related Recruiting Tests
Candidate Screening is the third scenario family in the Recruiting cluster, covering 22 individual scenarios that feed Interview and Job Offer downstream.
Turn This Standard Test into Your Oracle HCM Candidate Screening Regression Suite
Start with the Syntra Standard Candidate Screening test, use DataVault to provide environment-specific, masked or synthetic candidate, requisition and screening-question data, let Jarvis generate additional Positive, Negative and Security variations, and execute the resulting regression pack automatically with SyntraFlow.
Use This Oracle Fusion Test Case
Download Test Case
Excel, CSV or JSON export.
Coming soonAutomate with SyntraFlow
Run this script against your own tenant today.