Oracle Fusion Performance Completion Test Cases
Validate final completion rules, document locking, notifications, audit trail and downstream availability (e.g. to Compensation) of completed performance documents, without assuming every customer configures the same downstream integration — a catalog of 20 individual Performance Completion test scenarios spanning final completion rules, locking, notifications, downstream compensation availability and negative/security completion testing.
| Test ID | ORCL.HCM.PERF.COMPLETE |
| Application | Oracle Fusion Cloud |
| Product | HCM |
| Module | Performance Management |
| Process | Performance Completion |
| Business Flow | Performance-to-Compensation |
| 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 Performance Management 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 23 underlying Oracle Fusion UI actions to complete it.
Test Objective
This test validates final completion rules, document locking, notifications, audit trail and downstream availability (e.g. to Compensation) of completed performance documents.
The scenario should confirm that:
- the performance document completes correctly once the employee self-evaluation and manager evaluation stages are complete
- completion is correctly prevented when a required rating, comment or goal is missing or incomplete
- the final overall rating and final comments are recorded correctly on the completed document
- the completed document is correctly locked from further edits, and reopened only where configuration permits
- a completion notification is correctly triggered to the relevant participants
- the completed performance result is correctly made available downstream to Compensation where configured
- the completion audit trail and document history are correctly retained and visible to the employee and manager
- deliberately invalid completion attempts — missing rating, missing comment, incomplete goal, late completion, unauthorized worker — are correctly rejected or flagged rather than silently accepted
A negative or security Performance Completion scenario passes when Oracle correctly enforces the expected completion, locking or security rule; this test does not attempt to certify a specific Oracle application defect, and does not assume every customer configures downstream availability to Compensation identically — this depends entirely on customer-specific Oracle Fusion configuration. 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 20 individual Performance Completion scenarios as a single comprehensive reference rather than as separate indexable pages.
When to Use This Test
- Functional testing of final completion rules, locking and notifications for a new Oracle Fusion HCM Performance Management implementation
- Regression testing of completion and downstream Compensation availability after an Oracle quarterly update affecting Performance Management
- UAT sign-off for performance completion across final rating, locking, notification, reopen and audit-trail scenarios
- Baseline completion coverage referenced by Performance Document, Employee Evaluation and Manager Evaluation within the same Performance Management cluster
- Comprehensive scenario coverage for teams standardizing on a single Performance Completion regression pack instead of dozens of near-duplicate scripts
Where This Test Fits in the Performance-to-Compensation Process
Performance Completion is the fifth and final scenario family in the Performance Management cluster. It exercises final completion rules, document locking, completion notifications, completion-date validation, reopening where permitted, and downstream availability of the completed result to Compensation, together with negative and security validation. Exact locking behavior, reopen permissions and downstream availability to Compensation depend entirely on customer-specific Oracle Fusion Performance Management configuration — no universal downstream integration is assumed.
Preconditions
- Oracle Fusion Performance Management access is available to the manager test user.
- A representative ${WORKER} with a performance document in a ${DOCUMENT_STATUS} that has completed both the employee self-evaluation and manager evaluation stages is available, along with an assigned ${MANAGER}.
- A configured ${GOAL} set with all required sections populated is available on the worker's performance document for positive completion scenarios.
- A representative worker with a missing ${OVERALL_RATING}, missing comment or incomplete ${GOAL} is available for negative completion scenarios.
- A user without an authorized manager relationship to ${WORKER} is available for security testing.
- Where downstream availability to Compensation is configured, a valid ${COMPENSATION_CYCLE} is available for testing.
- Audit trail / history tracking (${AUDIT_LOG}) is enabled on the performance document for the review cycle.
Exact locking behavior, reopen permissions, completion notification routing and downstream availability to Compensation may vary by Oracle Fusion implementation and customer-specific configuration; no universal downstream integration is assumed.
Sample Test Data
| Worker | ${WORKER} |
| Manager | ${MANAGER} |
| Document Status | ${DOCUMENT_STATUS} |
| Overall Rating | ${OVERALL_RATING} |
| Completion Date | ${COMPLETION_DATE} |
| Goal | ${GOAL} |
| Compensation Cycle | ${COMPENSATION_CYCLE} |
| Audit Log | ${AUDIT_LOG} |
Sample values are illustrative ${PLACEHOLDER} tokens, not real worker, manager or rating data. Replace them with valid worker, manager and document 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 ~23 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.
| # | User Action | Expected Result |
|---|---|---|
| 1 | Sign In to Oracle Fusion HCM as Manager Sign in to Oracle Fusion Cloud with a user account that has manager access to Performance Management. | The Oracle Fusion Cloud home page loads successfully for the authenticated manager. |
| 2 | Confirm Employee and Manager Evaluations Are Complete Navigate to ${WORKER}'s performance document and confirm both the employee self-evaluation and ${MANAGER}'s evaluation are complete. ${WORKER} / ${MANAGER} | The performance document reflects a ${DOCUMENT_STATUS} showing both evaluation stages complete. |
| 3 | Verify All Required Sections and Ratings Are Present Review the performance document to confirm every required ${GOAL}, rating and comment section is populated before completion is attempted. ${GOAL} / ${OVERALL_RATING} | All required sections display as complete, or a missing item is correctly identified before completion is attempted. |
| 4 | Complete the Performance DocumentBusiness assertion Select the action to complete ${WORKER}'s performance document as of ${COMPLETION_DATE}. ${COMPLETION_DATE} Completion is correctly blocked for scenarios with a missing rating, comment or incomplete goal; this is a passing outcome for negative scenarios, not a failure. | The performance document completes successfully and updates to a completed ${DOCUMENT_STATUS}, or a deliberately incomplete attempt is correctly rejected with the expected validation. |
| 5 | Verify the Document Locks and Notification Triggers Confirm the completed document is locked from further edits (except where reopening is permitted) and that the configured completion notification is triggered to the relevant participants. | The document is correctly locked and the completion notification is correctly triggered, or the document correctly remains editable where reopening is permitted. |
| 6 | Verify Downstream Availability to Compensation Where configured, confirm the completed performance result for ${WORKER} is available to the ${COMPENSATION_CYCLE} downstream in Compensation. ${COMPENSATION_CYCLE} | The completed performance result is correctly available to Compensation where configured, or correctly withheld where downstream availability is not configured. |
| 7 | Verify Audit Trail and HistoryBusiness assertion Review the ${AUDIT_LOG} and performance history for ${WORKER} to confirm the completion event, completion date and prior evaluation stages are accurately recorded. ${AUDIT_LOG} This is the main business assertion for the scenario across the full catalog of 20 Performance Completion variations. | The audit trail and history accurately reflect a valid completion, or an expected validation for an invalid one. |
Expected Results
- Performance document completion recorded correctly once employee and manager evaluation stages are complete.
- Completion correctly prevented when a required rating, comment or goal is missing or incomplete.
- Final overall rating and final comments recorded correctly on the completed document.
- Completed document correctly locked from further edits, and reopened only where configuration permits.
- Completion notification correctly triggered to the relevant participants.
- Completed performance result correctly available downstream to Compensation where configured, and audit trail / history correctly retained.
Key Validation Checkpoints
- completion correctly blocked when required rating/comments/goals are incomplete
- completed document correctly locked from further edits (except where reopen is permitted)
- completion notification correctly triggered
- completed performance result correctly available to Compensation where configured
- document history and audit trail correctly retained
- unauthorized completion attempts correctly blocked
Go Beyond the Standard Test with Jarvis AI
The Syntra Standard Test Library defines the core Performance Completion scenario. Jarvis AI can extend this scenario by systematically generating additional Positive, Negative and Security variations using customer-specific worker, manager, rating and completion data available through Syntra DataVault.
Teams do not need to manually construct dozens of near-identical completion scenarios to cover every worker, rating, notification and downstream-availability combination. Jarvis uses the standard completion scenario as the foundation and generates coverage relevant to the customer's environment — these AI-generated variations do not create additional indexable SEO pages.
From Standard Test to Executed Regression Pack
Rather than maintaining a separate test for every possible completion, locking, notification and downstream-availability condition, SyntraFlow maintains one core Performance Completion scenario and allows Jarvis AI to generate Positive, Negative and Security variations using the customer's available worker, manager, rating and completion test data.
AI-Generated Test Variations
The same Performance Completion 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 Performance Management.
- Completion after employee and manager evaluation with all required sections
- Final rating and comments validation
- Document locking after completion
- Reopening where permitted
- Completion notification
- Downstream availability to Compensation and history retention
- Completion prevented with missing rating
- Completion prevented with missing comment
- Completion prevented with incomplete goal
- Late completion handling
- Manager attempts completion for an unauthorized worker
These are representative examples only. Locking behavior, reopen permissions, completion notification routing and downstream availability to Compensation can depend on the customer's Oracle Fusion configuration and Performance Management setup — not every Oracle configuration behaves identically.
Generated Using Your DataVault Test Data
Generic test data rarely represents every worker, rating, completion-date and downstream-availability combination in a real Oracle Fusion HCM Performance Management environment. Where connected, Jarvis can use approved test data available through Syntra DataVault — Worker, Manager, Document Status, Overall Rating, Completion Date, Goal and Compensation Cycle — to construct realistic Performance Completion variations relevant to the customer's actual implementation.
Standard Library Definition
Worker ${WORKER}
Manager ${MANAGER}
Document Status ${DOCUMENT_STATUS}
Overall Rating ${OVERALL_RATING}
Completion Date ${COMPLETION_DATE}
Goal ${GOAL}
Compensation Cycle ${COMPENSATION_CYCLE}
Audit Log ${AUDIT_LOG}
DataVault
Workers and Managers Workers with fully-evaluated performance documents and their assigned managers Document Status Documents at varying completion readiness, from incomplete to fully evaluated Ratings and Goals Final overall ratings, goal sets and comment completeness Compensation Cycles Configured compensation cycles for downstream availability testing Security Roles with and without an authorized manager relationship
Jarvis AI Generates
Standard "Performance Completion" + DataVault (Worker + Document Status + Rating + Compensation Cycle) → Jarvis generates: Scenario 01 — Complete Fully-Evaluated Document (Positive) Scenario 02 — Missing Required Rating (Negative) Scenario 03 — Manager Attempts to Complete Worker Outside Hierarchy (Security) Scenario 04 — Completed Result Available to Compensation Cycle (Positive) ...
Worker, rating and completion data used in Performance Completion testing are masked or synthetic wherever DataVault is connected — SyntraFlow test scenarios use ${PLACEHOLDER} tokens rather than real performance ratings, comments or worker data, and where DataVault masking and privacy controls are configured, they apply to the underlying customer test data used to generate variations across the Performance Completion catalog. See /datavault/data-masking/ for how DataVault protects performance data.
Example Test Variations
A comprehensive catalog of 20 individual Performance Completion test scenarios spanning final completion rules, locking, notifications, downstream compensation availability and negative/security completion testing. Filter or search below.
| ID | Variation | Type | Key Difference | Execution |
|---|---|---|---|---|
| PERF-CMP-001 | Complete Performance Document | Positive | Validate that ${MANAGER} can complete ${WORKER}'s performance document once all required sections are finished; Oracle Fusion updates the ${DOCUMENT_STATUS} to reflect a completed document. | SyntraFlow Ready |
| PERF-CMP-002 | Complete after Employee Evaluation | Positive | Validate that the performance document for ${WORKER} can be completed once the employee self-evaluation stage is finished; Oracle Fusion permits completion consistent with the configured review cycle sequence. | SyntraFlow Ready |
| PERF-CMP-003 | Complete after Manager Evaluation | Positive | Validate that the performance document for ${WORKER} can be completed once ${MANAGER}'s evaluation stage is finished; Oracle Fusion permits completion consistent with the configured review cycle sequence. | SyntraFlow Ready |
| PERF-CMP-004 | Complete with All Required Sections | Positive | Validate that ${WORKER}'s performance document, with every required ${GOAL}, rating and comment section populated, completes successfully; Oracle Fusion records the completed ${DOCUMENT_STATUS} without validation errors. | SyntraFlow Ready |
| PERF-CMP-005 | Prevent Completion with Missing Rating | Negative | Validate that attempting to complete ${WORKER}'s performance document with a required ${OVERALL_RATING} missing is handled correctly; Oracle Fusion raises the expected validation and does not accept the incomplete completion. | SyntraFlow Ready |
| PERF-CMP-006 | Prevent Completion with Missing Comment | Negative | Validate that attempting to complete ${WORKER}'s performance document with a required final comment missing is handled correctly; Oracle Fusion raises the expected validation rather than accepting the completion. | SyntraFlow Ready |
| PERF-CMP-007 | Prevent Completion with Incomplete Goal | Negative | Validate that attempting to complete ${WORKER}'s performance document with an incomplete ${GOAL} is handled correctly; Oracle Fusion raises the expected validation and prevents completion until the goal is finished. | SyntraFlow Ready |
| PERF-CMP-008 | Final Overall Rating Validation | Positive | Validate that the final ${OVERALL_RATING} recorded on ${WORKER}'s completed performance document is correct and consistent with the ratings entered during evaluation; Oracle Fusion records the final overall rating accurately. | SyntraFlow Ready |
| PERF-CMP-009 | Final Comments Validation | Positive | Validate that final comments recorded on ${WORKER}'s completed performance document are correctly captured and retained; Oracle Fusion records the final comments accurately against the completed document. | SyntraFlow Ready |
| PERF-CMP-010 | Performance Document Locked After Completion | Positive | Validate that ${WORKER}'s performance document is locked from further edits immediately after completion; Oracle Fusion correctly prevents further edits to a completed ${DOCUMENT_STATUS} document. | SyntraFlow Ready |
| PERF-CMP-011 | Reopen Completed Document Where Permitted | Positive | Validate that ${MANAGER} can reopen ${WORKER}'s completed performance document where reopening is permitted by configuration; Oracle Fusion updates the ${DOCUMENT_STATUS} and permits the intended edits. | SyntraFlow Ready |
| PERF-CMP-012 | Completion Notification | Positive | Validate that completing ${WORKER}'s performance document as of ${COMPLETION_DATE} correctly triggers the configured completion notification to the relevant participants; Oracle Fusion sends the expected notification. | SyntraFlow Ready |
| PERF-CMP-013 | Completion Date Validation | Positive | Validate that the ${COMPLETION_DATE} recorded on ${WORKER}'s performance document accurately reflects the date completion occurred; Oracle Fusion records the completion date correctly on the document. | SyntraFlow Ready |
| PERF-CMP-014 | Late Completion | Negative | Validate that completing ${WORKER}'s performance document after the configured due date is handled correctly; Oracle Fusion records the late completion and applies the expected configured handling rather than silently treating it as on time. | SyntraFlow Ready |
| PERF-CMP-015 | Manager Cannot Complete Unauthorized Worker | Negative/Security | Validate that a manager without an authorized relationship to ${WORKER} attempting to complete the worker's performance document is blocked; Oracle Fusion raises the expected security validation and prevents unauthorized completion. | SyntraFlow Ready |
| PERF-CMP-016 | Performance Result Available to Compensation Where Configured | Positive | Validate that, where configured, the completed performance result for ${WORKER} becomes available downstream to the ${COMPENSATION_CYCLE} in Compensation; Oracle Fusion correctly makes the completed result available where this integration is configured. | SyntraFlow Ready |
| PERF-CMP-017 | Performance History Retained | Positive | Validate that the performance history for ${WORKER}, including prior evaluation stages and the completion event, is correctly retained and viewable after completion; Oracle Fusion displays an accurate performance history. | SyntraFlow Ready |
| PERF-CMP-018 | Completed Document Visible to Employee | Positive | Validate that ${WORKER} can view their own completed performance document, including the final ${OVERALL_RATING} and comments, after completion; Oracle Fusion correctly displays the completed document to the employee. | SyntraFlow Ready |
| PERF-CMP-019 | Completed Document Visible to Manager | Positive | Validate that ${MANAGER} can view ${WORKER}'s completed performance document after completion; Oracle Fusion correctly displays the completed document to the authorized manager. | SyntraFlow Ready |
| PERF-CMP-020 | Completion Audit Trail | Positive | Validate that the ${AUDIT_LOG} for ${WORKER}'s performance document accurately records the completion event, ${COMPLETION_DATE} and responsible user; Oracle Fusion correctly retains a complete and accurate completion audit trail. | SyntraFlow Ready |
No variations match this filter.
Positive and Negative Performance Completion Testing
Positive Testing
Jarvis generates scenarios designed to confirm that Oracle Fusion HCM correctly completes, locks, notifies and makes available downstream a performance document when the worker, rating and completion data are all valid.
Fully-Evaluated Worker + Valid Overall Rating + Configured Compensation Cycle → Document Completed, Locked and Available Downstream
Negative Testing
Jarvis can also generate scenarios that deliberately violate a completion, eligibility or security rule to confirm Oracle correctly rejects or blocks the condition rather than silently accepting it.
- Missing Required Rating → Expected Validation Displayed
- Missing Required Comment → Expected Validation Displayed
- Incomplete Goal → Expected Validation Displayed
- Late Completion → Expected Handling Applied
- Unauthorized Manager Access → Access Prevented
A negative performance management scenario passes when Oracle correctly enforces the expected eligibility, template or security rule
| Scenario | Oracle Outcome | Test Result |
|---|---|---|
| Eligible worker document generated | Document created | PASS |
| Ineligible worker excluded | Validation occurs | PASS |
| Missing required rating | 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 Performance Completion scenarios and group them into reusable execution packs.
HCM Performance Completion Regression Pack
- Complete Performance Document
- Complete with All Required Sections
- Prevent Completion with Missing Rating
- Prevent Completion with Incomplete Goal
- Performance Document Locked After Completion
- Reopen Completed Document Where Permitted
- Completion Notification
- Manager Cannot Complete Unauthorized Worker
- Performance Result Available to Compensation Where Configured
- Completion Audit Trail
Run On-Demand or Schedule Automated Batch Execution
SyntraFlow can execute selected Performance Completion scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.
Once scheduled, SyntraFlow executes the selected Performance Completion scenarios unattended and records the outcome of each test and business assertion.
| Pack | HCM Performance Completion Regression Pack |
| Schedule | Weekly Regression |
| Tests | 20 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 performance completion — a pre-grouped, internally consistent set of worker, manager, rating, status and compensation-cycle dimensions, so Jarvis constructs realistic Performance Completion scenarios rather than combining incompatible data.
| Worker | ${WORKER} |
| Manager | ${MANAGER} |
| Document Status | ${DOCUMENT_STATUS} |
| Overall Rating | ${OVERALL_RATING} |
| Completion Date | ${COMPLETION_DATE} |
| Goal | ${GOAL} |
| Compensation Cycle | ${COMPENSATION_CYCLE} |
DataVault personas group dependent completion dimensions so Jarvis generates coherent, internally consistent Performance Completion scenarios rather than arbitrary and potentially unrepresentative field combinations.
Security & Access Variations
Oracle Fusion HCM Performance Management role and hierarchy configuration is customer-specific, so SyntraFlow can exercise completion access under different personas to confirm the customer's own access model behaves as expected, rather than assuming a universal Oracle security or manager hierarchy.
| Persona | Action | Expected | Syntra Result |
|---|---|---|---|
| Manager | Complete Direct Report's Document | Allowed | PASS |
| HR Specialist | Complete Document for Assigned Population | Allowed | PASS |
| Unauthorized Manager | Attempts to Complete Document for Worker Outside Hierarchy | 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 Performance Completion scenario, available DataVault test data and expected business outcomes to systematically generate Positive, Negative and Security coverage for the customer's environment.
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 performance document was correctly completed, locked or made available downstream — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution. Because this page aggregates 20 individual scenarios across final completion rules, locking, notifications, downstream compensation availability and negative/security validation, 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: Performance result not available to Compensation after completion — Likely category: INTEGRATION_ERROR / CONFIGURATION_ERROR — Evidence: the downstream Compensation integration or ${COMPENSATION_CYCLE} configuration does not reflect the completed document — Recommended action: verify the Compensation integration and cycle configuration 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 |
|---|---|---|
| Complete the Performance Document | Pass | — |
| Verify the Document Locks and Notification Triggers | Pass | — |
| Verify Audit Trail and History | Pass | Pass |
Related Performance Management Tests
Performance Completion is the fifth and final scenario family in the Performance Management cluster, covering 20 individual scenarios that build on Manager Evaluation and Employee Evaluation and close out the performance-to-compensation flow within Oracle Fusion HCM.
Turn This Standard Test into Your Oracle HCM Performance Completion Regression Suite
Start with the Syntra Standard Performance Completion test, use DataVault to provide environment-specific worker, manager and rating 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.