{
  "test_id": "ORCL.HCM.RECRUIT.APP",
  "scenario_name": "Candidate Application",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "Recruiting",
  "process": "Candidate Application",
  "business_flow": "Recruit-to-Hire",
  "scenario_type": "Positive / Negative / Boundary / Security",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/hcm/recruiting/candidate-application/",
  "objective": {
    "intro": "This test validates candidate profile creation, application submission, resume/document upload and application status tracking in Oracle Fusion HCM Recruiting, using only masked or synthetic candidate data — never real candidate PII.",
    "confirms": [
      "a candidate profile can be created and updated with synthetic profile, work experience, education and skills data",
      "an application can be submitted for a single or multiple requisitions and is correctly linked to the intended requisition",
      "internal, external, referred and job-board-sourced applications are all correctly received and attributed to their source",
      "a resume and supporting documents can be uploaded and parsed correctly into the candidate profile",
      "application status correctly progresses through review and withdrawal, whether initiated by the candidate or a recruiter",
      "deliberately invalid submissions — missing fields, invalid or oversized documents, duplicate or ineligible applications — are correctly rejected rather than silently accepted",
      "unauthorized users cannot access another candidate's profile"
    ],
    "scope_note": "A negative or boundary Candidate Application 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. This page catalogs 28 individual Candidate Application scenarios as a single comprehensive reference rather than as separate indexable pages, and every candidate data value referenced on this page is a synthetic ${PLACEHOLDER} token — never a real candidate's name, email, phone number or document."
  },
  "preconditions": [
    "Oracle Fusion Recruiting access is available to the test user.",
    "A configured ${REQUISITION} is open and accepting applications.",
    "A synthetic candidate profile for ${CANDIDATE} with ${CANDIDATE_EMAIL} and ${CANDIDATE_PHONE} exists or can be constructed, sourced only through Syntra DataVault.",
    "A synthetic ${RESUME_FILE} and supporting documents, in both valid and invalid formats, are available for document-handling testing.",
    "A closed requisition and a requisition past its posted closing date are available for negative eligibility testing.",
    "A duplicate-application condition can be constructed for an existing ${CANDIDATE} and ${REQUISITION}.",
    "A user without authorization to view another candidate's profile is available for security testing."
  ],
  "test_data": [
    {
      "field": "Candidate",
      "example": "${CANDIDATE}"
    },
    {
      "field": "Candidate Email",
      "example": "${CANDIDATE_EMAIL}"
    },
    {
      "field": "Candidate Phone",
      "example": "${CANDIDATE_PHONE}"
    },
    {
      "field": "Requisition",
      "example": "${REQUISITION}"
    },
    {
      "field": "Resume File",
      "example": "${RESUME_FILE}"
    },
    {
      "field": "Work Experience",
      "example": "${WORK_EXPERIENCE}"
    },
    {
      "field": "Education",
      "example": "${EDUCATION}"
    },
    {
      "field": "Skills",
      "example": "${SKILLS}"
    },
    {
      "field": "Application Source",
      "example": "${APPLICATION_SOURCE}"
    },
    {
      "field": "Referral",
      "example": "${REFERRAL}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Navigate to the Career Site or Internal Application",
      "action": "Navigate to the external career site, or the internal Recruiting application area, used to create a candidate profile and apply for a requisition.",
      "test_data": "${APPLICATION_SOURCE}",
      "expected_result": "The career site or internal application page loads successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Create or Update the Candidate Profile",
      "action": "Create a new candidate profile or update an existing one using synthetic candidate details, work experience, education and skills.",
      "test_data": "${CANDIDATE} / ${CANDIDATE_EMAIL} / ${CANDIDATE_PHONE} / ${WORK_EXPERIENCE} / ${EDUCATION} / ${SKILLS}",
      "expected_result": "The candidate profile is created or updated successfully with the entered synthetic details.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Upload Resume and Supporting Documents",
      "action": "Upload a synthetic resume and any supporting documents, such as a cover letter, to the candidate profile.",
      "test_data": "${RESUME_FILE}",
      "expected_result": "The resume and supporting documents upload successfully, or a deliberately invalid document is rejected with the expected validation.",
      "validation_type": "action",
      "note": "SyntraFlow always uses synthetic document content and never uploads a document containing real candidate PII."
    },
    {
      "step_number": 4,
      "step_name": "Select the Target Requisition",
      "action": "Select the requisition the candidate intends to apply for.",
      "test_data": "${REQUISITION}",
      "expected_result": "The correct requisition is selected and ready for application submission.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Submit the Application",
      "action": "Submit the completed application for the selected requisition, including source and referral attribution where applicable.",
      "test_data": "${APPLICATION_SOURCE} / ${REFERRAL}",
      "expected_result": "The application is submitted successfully, or a deliberately invalid submission is rejected with the expected validation.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify Application Status",
      "action": "Confirm the submitted application's status, including progression to In Review or Withdrawn where applicable.",
      "test_data": "${REQUISITION}",
      "expected_result": "Application status accurately reflects a valid submission, an expected progression, or an expected validation for an invalid submission.",
      "validation_type": "business_assertion",
      "note": "Correctly rejecting an invalid or ineligible application is a passing outcome for negative and boundary scenarios, not a failure."
    },
    {
      "step_number": 7,
      "step_name": "Verify Candidate Profile Data Integrity",
      "action": "Confirm that the candidate profile — including uploaded document data, parsed resume fields and application linkage — remains accurate and correctly scoped to authorized users only.",
      "test_data": "",
      "expected_result": "The candidate profile data is accurate, correctly linked to the application, and access remains restricted to authorized users.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario across the full catalog of 28 Candidate Application variations."
    }
  ],
  "expected_results": [
    "Each candidate profile is created, updated and retrievable with the correct synthetic profile, work-experience, education and skills data.",
    "Each application is correctly linked to the intended requisition, whether internal, external, referred or sourced via job-board integration.",
    "Resume and supporting document uploads are stored correctly, and resume data is parsed accurately into profile fields.",
    "Application status correctly progresses through review and withdrawal states.",
    "Deliberately invalid submissions — missing fields, invalid or oversized documents, duplicate or ineligible applications — raise the expected validation rather than being silently accepted.",
    "Unauthorized users are correctly prevented from accessing another candidate's profile."
  ],
  "validation_checkpoints": [
    "Candidate profile correctly created and retrievable.",
    "Application correctly linked to the intended requisition.",
    "Document upload and parsing correctly reflected in the profile.",
    "Duplicate applications correctly blocked.",
    "Closed/expired requisitions correctly reject new applications.",
    "Unauthorized profile access correctly blocked."
  ]
}