Oracle ERP Testing Tool > Test Library > HCM > Performance Management
Syntra Standard Oracle Test Library

Oracle Fusion Performance Document Test Cases

Validate creation, eligibility, section content and status lifecycle of performance documents across review periods and templates, without assuming a universal template or rating-scale structure — a comprehensive catalog of 40 individual Performance Document test scenarios, the first and largest family page in the new Performance Management cluster, spanning creation and setup, eligibility, section content, negative and exception handling, and document status lifecycle.

Test IDORCL.HCM.PERF.DOCUMENT
ApplicationOracle Fusion Cloud
ProductHCM
ModulePerformance Management
ProcessPerformance Document
Business FlowPerformance-to-Compensation
Scenario TypePositive / Negative / Security
Test UsageFunctional Testing / Regression Testing / UAT Sign-Off
PriorityHigh
AutomationSyntraFlow Ready
LibrarySyntra 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 28 underlying Oracle Fusion UI actions to complete it.

Test Objective

This test validates creation, eligibility, section content and status lifecycle of performance documents across review periods and templates, without assuming a universal template or rating-scale structure.

The scenario should confirm that:

  • each performance document can be generated correctly for an eligible worker from the configured performance template and review period
  • worker eligibility rules — new hire, terminated, contingent, multiple assignments and manager population — are correctly applied when documents are generated
  • required and optional sections configured on the template (ratings, comments, goals, competencies and development where configured) are correctly present on the generated document
  • document status correctly progresses through created, in progress, submitted, returned and completed as the performance cycle advances
  • document history is retained and accurately reflects prior status transitions
  • deliberately invalid conditions — invalid or inactive template, invalid review period, missing manager, duplicate generation, invalid effective date, unauthorized access and generation process failure — are correctly rejected or flagged rather than silently accepted

A negative performance management scenario passes when Oracle correctly enforces the expected eligibility, template or security rule; this test does not attempt to certify a specific Oracle application defect, and does not assume a universal performance template or rating scale — both depend 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 40 individual Performance Document scenarios — the first and largest catalog in the new Performance Management cluster — as a single comprehensive reference rather than as separate indexable pages.

When to Use This Test

  • Functional testing of performance document creation and eligibility for a new Oracle Fusion HCM Performance Management implementation
  • Regression testing of performance document generation and section content after an Oracle quarterly update affecting Performance Management
  • UAT sign-off for performance documents across creation, eligibility, section content and status lifecycle scenarios
  • Baseline performance document coverage referenced by Employee Evaluation and Manager Evaluation within the same Performance Management cluster
  • Comprehensive scenario coverage for teams standardizing on a single Performance Document regression pack instead of dozens of near-duplicate scripts

Where This Test Fits in the Performance-to-Compensation Process

Performance Document
Employee Evaluation
Manager Evaluation
Compensation

Performance Document is the first and largest scenario family in the new Performance Management cluster. It exercises document creation and setup, eligibility, section content and status lifecycle, together with negative and security validation, and feeds Employee Evaluation and Manager Evaluation downstream, which in turn inform Compensation. Exact template structure, rating scale, section configuration and eligibility rules depend entirely on customer-specific Oracle Fusion Performance Management configuration — no universal template or rating scale is assumed.

Preconditions

  1. Oracle Fusion Performance Management access is available to the test user.
  2. A representative ${WORKER} and ${MANAGER}, including new hire and terminated worker records, are available or can be constructed.
  3. A configured ${PERFORMANCE_TEMPLATE} for the applicable ${REVIEW_PERIOD}, including required and optional sections, is available.
  4. A defined ${WORKER_POPULATION} reflecting the eligibility rules to be tested (new hire, contingent, multiple assignments) is available.
  5. Representative ${GOAL} and ${COMPETENCY} records linked to the applicable workers are available where the template includes those sections.
  6. A configured ${RATING_SCALE} for the applicable performance template is in place.
  7. A user without the required Performance Management security access is available for security testing, and an inactive or invalid ${PERFORMANCE_TEMPLATE} is available for negative testing.

Exact template structure, rating scale, section configuration and eligibility rules may vary by Oracle Fusion implementation and customer-specific configuration; no universal performance template or rating scale is assumed.

Sample Test Data

Worker${WORKER}
Manager${MANAGER}
Review Period${REVIEW_PERIOD}
Performance Template${PERFORMANCE_TEMPLATE}
Worker Population${WORKER_POPULATION}
Goal${GOAL}
Competency${COMPETENCY}
Document Status${DOCUMENT_STATUS}
Effective Date${EFFECTIVE_DATE}
Rating Scale${RATING_SCALE}

Sample values are illustrative ${PLACEHOLDER} tokens, not real worker, rating or review data. Replace them with valid worker, template and review period 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 ~28 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.

#User ActionExpected Result
1
Sign In to Oracle Fusion HCM
Sign in to Oracle Fusion Cloud with a user account that has Performance Management access.
The Oracle Fusion Cloud home page loads successfully for the authenticated user.
2
Navigate to Performance Management
Navigate to the Performance Management work area used to create and manage performance documents.
The Performance Management work area opens successfully.
3
Select Review Period and Eligible Worker Population
Select the ${REVIEW_PERIOD} and the ${WORKER_POPULATION} eligible for the performance cycle.
${REVIEW_PERIOD} / ${WORKER_POPULATION}
The selected review period and eligible worker population are correctly recorded for document generation.
4
Generate Performance Documents from Configured Template
Generate performance documents for the eligible worker population from the configured ${PERFORMANCE_TEMPLATE}.
${PERFORMANCE_TEMPLATE}

Exact eligibility and template behavior depends on the customer's own Performance Management configuration.

Performance documents are generated for eligible workers from the configured template, or a deliberately invalid condition is correctly rejected or flagged.
5
Verify Goals, Competencies and Sections Populate CorrectlyBusiness assertion
Verify that goals, competencies and other required or optional sections populate correctly on the generated document according to the template configuration.
${GOAL} / ${COMPETENCY}
Required and optional sections correctly reflect the template configuration for each generated document.
6
Verify Document StatusBusiness assertion
Verify that each performance document reflects the correct status as it moves through the performance cycle.
${DOCUMENT_STATUS}
Document status accurately reflects created, in progress, submitted, returned or completed as appropriate.
7
Verify Document History Is RetainedBusiness assertion
Confirm that the performance document's history accurately retains prior status transitions and key changes.

This is the main business assertion for the scenario across the full catalog of 40 Performance Document variations.

Document history correctly reflects the sequence of status transitions for the document.

Expected Results

  • Each performance document correctly generated for eligible workers per the configured template and review period.
  • Ineligible workers correctly excluded from document generation.
  • Required sections correctly present on the generated document per template configuration.
  • Document status correctly reflected the appropriate lifecycle stage as the cycle progressed.
  • Duplicate document generation correctly prevented for the same worker and review period.
  • Unauthorized access to another worker's performance document correctly blocked.

Key Validation Checkpoints

  • Document correctly generated for eligible workers per configured template and period.
  • Ineligible workers correctly excluded.
  • Required sections correctly present per template configuration.
  • Document status correctly reflects lifecycle stage.
  • Duplicate generation correctly prevented.
  • Unauthorized access correctly blocked.
Core Business Scenario
Performance Document
Scenario Catalog
40 Scenarios
Business Steps
7
Test Data
DataVault-Driven
Execution
On-Demand / Scheduled / Batch
Automation
SyntraFlow Ready
Jarvis AI

Go Beyond the Standard Test with Jarvis AI

The Syntra Standard Test Library defines the core Performance Document scenario. Jarvis AI can extend this scenario by systematically generating additional Positive, Negative and Security variations using customer-specific worker, manager, template and review period data available through Syntra DataVault.

Teams do not need to manually construct dozens of near-identical document scenarios to cover every worker population, template and status transition combination. Jarvis uses the standard performance document scenario as the foundation and generates coverage relevant to the customer's environment — without creating additional indexable pages.

From Standard Test to Executed Regression Pack

01
Syntra Standard Test
Reusable Performance Document scenario and automation logic.
02
Customer DataVault
Provides approved customer-specific test data required for variation generation — Worker, Manager, Review Period, Performance Template, Worker Population, Goal, Competency and Document Status.
03
Jarvis AI
Analyses the standard performance document scenario together with available test data and generates Positive, Negative and Security variations.
04
Positive + Negative + Security Variations
Correctly generated and progressed documents and deliberately invalid, unauthorized or misconfigured conditions.
05
Regression Pack
Selected variations can be grouped into an executable suite.
06
On-Demand / Scheduled / Batch Execution
Execute immediately or schedule the regression pack for unattended batch execution.
07
Results + Evidence + Exceptions
Capture execution results, business assertions, screenshots/evidence and exception classification.

Rather than maintaining a separate test for every possible performance document creation, eligibility and status condition, SyntraFlow maintains one core Performance Document scenario and allows Jarvis AI to generate Positive, Negative and Security variations using the customer's available worker, template and review period test data.

AI-Generated Test Variations

The same Performance Document 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.

Positive Scenarios
  • Standard performance document creation and generation for eligible workers and worker populations
  • Goals and competencies content included on generated documents
  • Documents generated across different templates and review periods
  • Eligibility correctly applied for new hire and multiple-assignment workers
  • Required and optional section display per template configuration
  • Status lifecycle progression — created, in progress, submitted, completed
  • Document history retained across status transitions
Negative Scenarios
  • Ineligible worker excluded from document generation
  • Invalid or inactive performance template
  • Invalid review period or effective date
  • Missing manager on the performance document
  • Duplicate document generation for the same worker and review period
  • Unauthorized document access

These are representative examples only. Template structure, rating scale, section configuration and eligibility rules can depend on the customer's Oracle Fusion Performance Management configuration — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely represents every worker, template and review period combination in a real Oracle Fusion HCM Performance Management environment. Where connected, Jarvis can use approved test data available through Syntra DataVault — Worker, Manager, Review Period, Performance Template, Goal and Competency — to construct realistic Performance Document variations relevant to the customer's actual implementation.

Standard Library Definition

Worker                 ${WORKER}
Manager                ${MANAGER}
Review Period          ${REVIEW_PERIOD}
Performance Template   ${PERFORMANCE_TEMPLATE}
Worker Population      ${WORKER_POPULATION}
Goal                   ${GOAL}
Competency             ${COMPETENCY}
Document Status        ${DOCUMENT_STATUS}
Effective Date         ${EFFECTIVE_DATE}
Rating Scale           ${RATING_SCALE}

DataVault

Workers and Eligibility
  Workers with new hire, terminated, contingent and multiple-assignment eligibility profiles
Templates
  Performance templates with valid, inactive and misconfigured section combinations
Review Periods
  Current, future-dated and invalid review period definitions
Sections
  Ratings, comments, goals, competencies and development section configurations
Security
  Roles with and without document generation and access authorization

Jarvis AI Generates

Scenario 01 — Standard Document Generation
Scenario 02 — Multiple Workers, Same Template
Scenario 03 — Ineligible Worker Excluded
Scenario 04 — Missing Manager
Scenario 05 — Duplicate Document Generation
Scenario 06 — Unauthorized Document Access
...

Performance Document test data can include worker, manager and rating information. SyntraFlow test scenarios use ${PLACEHOLDER} tokens rather than real performance ratings or comments tied to real people, and where DataVault masking and privacy controls are configured, they apply to the underlying customer test data used to generate variations across the Performance Document catalog — see /datavault/data-masking/ for how DataVault protects worker and rating data.

Example Test Variations

A comprehensive catalog of 40 individual Performance Document test scenarios spanning creation/setup, eligibility, section content, negative/exception handling and document status lifecycle. Filter or search below.

IDVariationTypeKey DifferenceExecution
PERF-DOC-001Create Performance DocumentPositiveValidate that a performance document can be created for ${WORKER} using the configured ${PERFORMANCE_TEMPLATE} and ${REVIEW_PERIOD}; Oracle Fusion creates the document with the template and review period correctly recorded.SyntraFlow Ready
PERF-DOC-002Generate Performance Document for Eligible WorkerPositiveValidate that a performance document is correctly generated for an eligible ${WORKER} within the ${WORKER_POPULATION}; Oracle Fusion generates the document for the eligible worker as expected.SyntraFlow Ready
PERF-DOC-003Generate Documents for Multiple WorkersPositiveValidate that performance documents can be generated in a single run for multiple workers within the ${WORKER_POPULATION}; Oracle Fusion generates a correctly populated document for each eligible worker.SyntraFlow Ready
PERF-DOC-004Different Review PeriodPositiveValidate that performance documents can be generated for a different ${REVIEW_PERIOD} than the current cycle; Oracle Fusion correctly associates each generated document with the selected review period.SyntraFlow Ready
PERF-DOC-005Different Performance TemplatePositiveValidate that performance documents can be generated using a different ${PERFORMANCE_TEMPLATE} configured for ${WORKER_POPULATION}; Oracle Fusion correctly applies the selected template's structure to the generated document.SyntraFlow Ready
PERF-DOC-006Different Worker PopulationPositiveValidate that performance documents can be generated for a differently defined ${WORKER_POPULATION}, such as a specific department or job family; Oracle Fusion correctly generates documents for the workers within the selected population.SyntraFlow Ready
PERF-DOC-007Performance Document with GoalsPositiveValidate that a performance document generated for ${WORKER} correctly includes the ${GOAL} content configured on the applicable ${PERFORMANCE_TEMPLATE}; Oracle Fusion populates the goals content on the document correctly.SyntraFlow Ready
PERF-DOC-008Performance Document with CompetenciesPositiveValidate that a performance document generated for ${WORKER} correctly includes the ${COMPETENCY} content configured on the applicable ${PERFORMANCE_TEMPLATE}; Oracle Fusion populates the competencies content on the document correctly.SyntraFlow Ready
PERF-DOC-009Performance Document with Goals + CompetenciesPositiveValidate that a performance document generated for ${WORKER} correctly includes both ${GOAL} and ${COMPETENCY} content where the ${PERFORMANCE_TEMPLATE} configures both sections; Oracle Fusion populates both sections on the document correctly.SyntraFlow Ready
PERF-DOC-010Future-Dated Performance CyclePositiveValidate that a performance document can be generated for a future-dated ${REVIEW_PERIOD} with an ${EFFECTIVE_DATE} later than the current date; Oracle Fusion correctly generates the document for the future-dated cycle.SyntraFlow Ready
PERF-DOC-011Eligible Worker Receives DocumentPositiveValidate that an eligible ${WORKER} within the configured ${WORKER_POPULATION} correctly receives a generated performance document; Oracle Fusion correctly includes the eligible worker in the generation run.SyntraFlow Ready
PERF-DOC-012Ineligible Worker ExcludedNegativeValidate that a ${WORKER} who does not meet the eligibility criteria for the ${WORKER_POPULATION} is correctly excluded from document generation; Oracle Fusion correctly omits the ineligible worker rather than generating a document in error.SyntraFlow Ready
PERF-DOC-013New Hire EligibilityPositiveValidate that a newly hired ${WORKER} is correctly evaluated against the eligibility rules for the ${REVIEW_PERIOD}; Oracle Fusion correctly includes or excludes the new hire according to the configured eligibility rule.SyntraFlow Ready
PERF-DOC-014Terminated Worker HandlingPositiveValidate that a terminated ${WORKER} is handled correctly when performance documents are generated for the ${REVIEW_PERIOD}; Oracle Fusion correctly applies the configured rule for terminated workers rather than generating an unintended document.SyntraFlow Ready
PERF-DOC-015Contingent Worker Handling Where ConfiguredPositiveValidate that a contingent ${WORKER}, where contingent workers are included in Performance Management configuration, is handled correctly during document generation for the ${WORKER_POPULATION}; Oracle Fusion applies the configured contingent-worker eligibility rule correctly.SyntraFlow Ready
PERF-DOC-016Worker with Multiple AssignmentsPositiveValidate that a ${WORKER} with multiple assignments is handled correctly when a performance document is generated; Oracle Fusion correctly associates the document with the appropriate assignment per configuration.SyntraFlow Ready
PERF-DOC-017Manager Population EligibilityPositiveValidate that eligibility for a performance document correctly reflects the ${MANAGER}'s population, such as direct reports only or including indirect reports where configured; Oracle Fusion correctly applies the configured manager population rule.SyntraFlow Ready
PERF-DOC-018Required Section DisplayedPositiveValidate that a section marked required on the ${PERFORMANCE_TEMPLATE} is correctly displayed on the generated document for ${WORKER}; Oracle Fusion correctly renders the required section.SyntraFlow Ready
PERF-DOC-019Optional Section DisplayedPositiveValidate that a section marked optional on the ${PERFORMANCE_TEMPLATE} is correctly displayed or omitted according to configuration on the generated document for ${WORKER}; Oracle Fusion correctly handles the optional section.SyntraFlow Ready
PERF-DOC-020Rating SectionPositiveValidate that the rating section on the generated document correctly reflects the configured ${RATING_SCALE} for the ${PERFORMANCE_TEMPLATE}; Oracle Fusion correctly renders the rating section per the configured scale.SyntraFlow Ready
PERF-DOC-021Comments SectionPositiveValidate that the comments section on the generated document for ${WORKER} correctly accepts and retains entered comments; Oracle Fusion correctly records the comments section content.SyntraFlow Ready
PERF-DOC-022Goals SectionPositiveValidate that the goals section on the generated document correctly reflects the ${GOAL} records associated with ${WORKER}; Oracle Fusion correctly populates the goals section.SyntraFlow Ready
PERF-DOC-023Competencies SectionPositiveValidate that the competencies section on the generated document correctly reflects the ${COMPETENCY} records associated with ${WORKER}; Oracle Fusion correctly populates the competencies section.SyntraFlow Ready
PERF-DOC-024Development Section Where ConfiguredPositiveValidate that a development section, where configured on the ${PERFORMANCE_TEMPLATE}, is correctly displayed and populated on the generated document for ${WORKER}; Oracle Fusion correctly renders the development section where it is part of the template.SyntraFlow Ready
PERF-DOC-025Invalid TemplateNegativeValidate that attempting to generate a performance document using an invalid ${PERFORMANCE_TEMPLATE} reference is handled correctly; Oracle Fusion raises the expected data validation rather than generating the document.SyntraFlow Ready
PERF-DOC-026Inactive TemplateNegativeValidate that attempting to generate a performance document using an inactive ${PERFORMANCE_TEMPLATE} is handled correctly; Oracle Fusion raises the expected configuration validation rather than generating the document from the inactive template.SyntraFlow Ready
PERF-DOC-027Invalid Review PeriodNegativeValidate that attempting to generate a performance document for an invalid or unconfigured ${REVIEW_PERIOD} is handled correctly; Oracle Fusion raises the expected data validation rather than generating the document.SyntraFlow Ready
PERF-DOC-028Missing ManagerNegativeValidate that generating a performance document for a ${WORKER} without an assigned ${MANAGER} is handled correctly; Oracle Fusion raises the expected validation rather than generating a document with an incomplete hierarchy.SyntraFlow Ready
PERF-DOC-029Worker Not EligibleNegativeValidate that attempting to generate a performance document directly for a ${WORKER} who does not meet the configured eligibility rule is handled correctly; Oracle Fusion correctly prevents or flags the generation rather than creating the document.SyntraFlow Ready
PERF-DOC-030Duplicate Document GenerationNegativeValidate that attempting to generate a second performance document for the same ${WORKER} and ${REVIEW_PERIOD} is handled correctly; Oracle Fusion correctly prevents or flags the duplicate generation.SyntraFlow Ready
PERF-DOC-031Unauthorized Document AccessNegative/SecurityValidate that a user without the required Performance Management security access attempting to open ${WORKER}'s performance document is blocked; Oracle Fusion raises the expected security validation and prevents the unauthorized access.SyntraFlow Ready
PERF-DOC-032Template Missing Required SectionNegativeValidate that a ${PERFORMANCE_TEMPLATE} misconfigured without a required section is handled correctly when a document is generated; Oracle Fusion raises the expected configuration validation rather than generating an incomplete document.SyntraFlow Ready
PERF-DOC-033Invalid Effective DateNegativeValidate that generating a performance document with an invalid ${EFFECTIVE_DATE}, such as a date outside the configured ${REVIEW_PERIOD}, is handled correctly; Oracle Fusion raises the expected data validation rather than accepting the invalid date.SyntraFlow Ready
PERF-DOC-034Generation Process FailureNegativeValidate that an unexpected failure during the performance document generation process for ${WORKER_POPULATION} is handled correctly; Oracle Fusion or SyntraFlow's evidence correctly surfaces the failure rather than silently completing an incomplete run.SyntraFlow Ready
PERF-DOC-035Document Created StatusPositiveValidate that a newly generated performance document for ${WORKER} correctly shows a ${DOCUMENT_STATUS} of Created; Oracle Fusion correctly sets the initial document status.SyntraFlow Ready
PERF-DOC-036Document In ProgressPositiveValidate that a performance document for ${WORKER} correctly transitions to an In Progress ${DOCUMENT_STATUS} once content entry has begun; Oracle Fusion correctly updates the document status.SyntraFlow Ready
PERF-DOC-037Document SubmittedPositiveValidate that a performance document for ${WORKER} correctly transitions to a Submitted ${DOCUMENT_STATUS} once submitted by the ${MANAGER} or worker as configured; Oracle Fusion correctly records the submission status.SyntraFlow Ready
PERF-DOC-038Document ReturnedPositiveValidate that a submitted performance document for ${WORKER} can be correctly returned for revision, updating the ${DOCUMENT_STATUS} to Returned; Oracle Fusion correctly records the returned status and reopens the document for edits.SyntraFlow Ready
PERF-DOC-039Document CompletedPositiveValidate that a performance document for ${WORKER} correctly transitions to a Completed ${DOCUMENT_STATUS} once the performance cycle is finalized; Oracle Fusion correctly records the completed status.SyntraFlow Ready
PERF-DOC-040Document HistoryPositiveValidate that the performance document for ${WORKER} correctly retains a history of ${DOCUMENT_STATUS} transitions across the performance cycle; Oracle Fusion correctly preserves the document's status history.SyntraFlow Ready

Positive and Negative Performance Document Testing

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion HCM correctly creates and progresses a performance document when the worker, manager, template, review period and eligibility are all valid.

Eligible Worker + Valid Template + Configured Review Period → Document Generated with Correct Sections and Status

Negative Testing

Jarvis can also generate scenarios that deliberately violate an eligibility, template or security rule to confirm Oracle correctly rejects or flags the condition rather than silently accepting it.

  • Ineligible Worker → Expected Exclusion from Generation
  • Invalid Template → Expected Data Validation Displayed
  • Inactive Template → Expected Configuration Validation Displayed
  • Missing Manager → Expected Validation Displayed
  • Duplicate Document Generation → Expected Validation Displayed
  • Unauthorized User → Access Prevented

A negative performance management scenario passes when Oracle correctly enforces the expected eligibility, template or security rule

ScenarioOracle OutcomeTest Result
Eligible worker document generatedDocument createdPASS
Ineligible worker excludedValidation occursPASS
Missing required ratingValidation occursPASS
Unauthorized userAccess preventedPASS
Unexpected application exceptionUnexpected failureFAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated Performance Document scenarios and group them into reusable execution packs.

HCM Performance Document Regression Pack

  • Create Performance Document
  • Generate Performance Document for Eligible Worker
  • Generate Documents for Multiple Workers
  • Performance Document with Goals + Competencies
  • Required Section Displayed
  • Rating Section
  • Ineligible Worker Excluded
  • Missing Manager
  • Unauthorized Document Access
  • Document Completed
Add Selected to Regression Pack(coming soon)Run Now(coming soon)Schedule(coming soon)

Run On-Demand or Schedule Automated Batch Execution

SyntraFlow can execute selected Performance Document scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected Performance Document scenarios unattended and records the outcome of each test and business assertion.

Run immediatelyNightly regressionWeekly regressionBefore releaseAfter configuration changesAfter environment refreshQuarterly Oracle update testingPre-UAT validation
PackHCM Performance Document Regression Pack
ScheduleWeekly Regression
Tests40 scenarios
ExecutionBatch Mode
Start9:00 PM
EnvironmentOracle Fusion TEST
StatusScheduled

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.

40
Total Scenarios
36
Passed
3
Failed
1
Exceptions
29
Positive Tests
11
Negative Tests
280
Business Assertions

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 documents — a pre-grouped, internally consistent set of worker, manager, template and review period dimensions, so Jarvis constructs realistic Performance Document scenarios rather than combining incompatible data.

Persona: Eligible Performance-Cycle Worker
Worker${WORKER}
Manager${MANAGER}
Review Period${REVIEW_PERIOD}
Performance Template${PERFORMANCE_TEMPLATE}
Worker Eligibility${WORKER_ELIGIBILITY}
Goal${GOAL}
Competency${COMPETENCY}
Document Status${DOCUMENT_STATUS}

DataVault personas group dependent performance management dimensions so Jarvis generates coherent, internally consistent Performance Document scenarios rather than arbitrary and potentially unrepresentative field combinations.

Security & Access Variations

Oracle Fusion HCM Performance Management role and security configuration is customer-specific, so SyntraFlow can exercise document generation and access under different personas to confirm the customer's own access model behaves as expected, rather than assuming a universal Oracle security model.

PersonaActionExpectedSyntra Result
ManagerAccess Direct Report's Performance DocumentAllowedPASS
HR SpecialistGenerate Documents for Assigned PopulationAllowedPASS
Unauthorized UserAttempts to Access Another Worker's DocumentAccess preventedPASS

Understand Why a Test Failed

SyntraFlow execution evidence can help distinguish business-data failures, configuration issues, automation problems and potential application defects.

DataConfigurationSecurityAutomationApplicationEnvironmentExpected Validation
Jarvis Failure Intelligence — Coming Soon

From Business Scenario to Execution Evidence

Business teams get readable test documentation; automation teams retain detailed execution traceability.

Standard Business Scenario
AI-Generated Variation
Regression Pack
Business Test Step
Automation Actions
Business Assertion
Screenshot / Evidence
Execution Result

Meet Jarvis — SyntraFlow's AI Testing Engine

Jarvis extends the Syntra Standard Test Library by analysing the Performance Document scenario, available DataVault test data and expected business outcomes to systematically generate Positive, Negative and Security coverage for the customer's environment.

Generate
Positive, Negative and Security variations.
Parameterize
Use relevant worker, template and review period data from DataVault.
Assemble
Build reusable regression packs.
Execute
Run scenarios autonomously.
Schedule
Execute unattended test batches.
Validate
Evaluate expected business outcomes.

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.

Standard Library — Performance Document, 7 Business Steps
DataVault — HCM Persona-Specific Test Data
Jarvis AI — Generate Positive/Negative/Security Variations
Regression Pack — Select Relevant Coverage
SyntraFlow Execution — Each Variation
Detailed UI Actions
Business Assertions
Evidence
PASS / FAIL

Business Step → Underlying UI Actions

Business Step
Generate Performance Documents from Configured Template
May internally include
Open Performance Document Generation → Select Template → Select Review Period → Select Worker Population → Run Generation Process → Capture Status
Business Step
Verify Document Status
May internally include
Open Performance Document → Read Status Field → Compare to Expected Lifecycle Stage → Capture Evidence

What SyntraFlow Captures Per Run

Parameterised input valuesReusable navigationAutomation action traceScreenshots / evidence captureExecution timingPass / fail statusBusiness assertionsEnvironment-independent test data

Action Status vs. Business Validation

A successful UI interaction does not automatically prove a performance document was correctly generated, populated or progressed through status — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution. Because this page aggregates 40 individual scenarios across creation and setup, eligibility, section content, negative and exception handling, and document status lifecycle, 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 document missing due to worker not eligible — Likely category: DATA_ERROR / CONFIGURATION_ERROR — Evidence: the worker's eligibility criteria for the configured worker population do not match the underlying assignment or eligibility profile data — Recommended action: verify worker eligibility configuration and assignment data before resubmitting. A failure should not be labeled as an Oracle application defect until data, configuration, security, automation and integration causes have been eliminated.

StepAction StatusBusiness Validation
Generate Performance Documents from Configured TemplatePass
Verify Goals, Competencies and Sections Populate CorrectlyPassPass
Verify Document StatusPassPass

Related Performance Management Tests

Performance Document is the first, largest scenario family in the new Performance Management cluster, covering 40 individual scenarios that feed Employee Evaluation and Manager Evaluation downstream.

Turn This Standard Test into Your Oracle HCM Performance Document Regression Suite

Start with the Syntra Standard Performance Document test, use DataVault to provide environment-specific worker, manager and template 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 soon

Automate with SyntraFlow

Run this script against your own tenant today.

Frequently Asked Questions

How many test scenarios does this Performance Document catalog cover, and why are they grouped on one page?
This page catalogs 40 individual Performance Document test scenarios — the first and largest catalog in the new Performance Management cluster — spanning creation and setup, eligibility, section content, negative and exception handling, and document status lifecycle. They are grouped on a single page rather than published as 40 separate URLs so search engines and users find one authoritative, comprehensive reference for Performance Document rather than dozens of thin near-duplicate pages; every scenario remains individually executable within SyntraFlow.
Does SyntraFlow assume a universal eligibility rule for performance documents?
No. Worker eligibility for performance document generation — including new hire, terminated, contingent worker, multiple assignment and manager population rules — depends entirely on the customer's own Oracle Fusion Performance Management configuration. SyntraFlow's scenarios are designed to validate whatever eligibility rules are actually configured rather than certifying a single, universal eligibility model.
Are the performance template and rating scale assumed to be the same for every customer?
No. Template structure, required and optional sections, and the rating scale used on a performance document are configured per customer and can vary by worker population, job family or business unit. SyntraFlow's scenarios validate document content against whatever template and rating scale are actually configured rather than assuming a universal structure.
How does SyntraFlow test the document status lifecycle?
Dedicated scenarios confirm that a performance document correctly reflects Created, In Progress, Submitted, Returned and Completed status as it moves through the performance cycle, and that document history accurately retains the sequence of prior status transitions.
How does SyntraFlow classify a failed Performance Document test?
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 — along with supporting evidence and a recommended action. A failure should not be labeled as an Oracle application defect until data, configuration, security, automation and integration causes have been eliminated.
How is security tested for Performance Document?
SyntraFlow can exercise document generation and access under different personas — a Manager accessing a direct report's document, an HR Specialist generating documents for an assigned worker population, and an unauthorized user attempting to access another worker's document — to confirm Oracle correctly allows or blocks the action. Actual behavior depends on the customer's own Oracle Fusion Performance Management security configuration.