This list contains only the countries for which job offers have been published in the selected language (e.g., in the French version, only job offers written in French are displayed, and in the English version, only those in English).
We are building a dedicated QA automation function, starting with monthly patch validation for Oracle EBS and growing to cover the full Oracle EBS ecosystem. You will work with Claude Code and Playwright MCP to automate complex multi-step workflows across Oracle EBS modules — including ERS, Supplier management, iProc, Payments, Lease, and more. Clean object-oriented design is a first-class requirement: the codebase you write today will be the foundation others extend for years. You will also design data-driven test frameworks to maximize coverage with minimal duplication, and act as a quality gatekeeper — logging and reporting any defects you uncover while building or running test scripts.
Job Responsibility
Design and implement Playwright-based end-to-end test scripts for Oracle EBS modules using an OOP architecture (page objects, component classes, shared fixtures)
Use Claude Code with Playwright MCP to accelerate test authoring, selector generation, and script iteration
Build reusable, maintainable test utilities — auth helpers, data factories, retry strategies, and wait utilities — that work across the full Oracle EBS surface
Own GitLab CI/CD pipeline integration: configure test jobs, manage parallelism, and maintain a reliable pass/fail reporting baseline
Triage flaky tests and selector failures caused by OAF/Apex UI quirks (dynamic IDs, iFrames, popup handling) and implement robust fixes
Collaborate on test scope planning for each monthly patch cycle and contribute to expanding coverage to new EBS modules over time
Document automation patterns, contribute to an internal wiki, and participate in code reviews with a focus on maintainability and readability
Design and implement data-driven test frameworks — externalizing test inputs into structured data sets (JSON, CSV, or Excel) so a single test class exercises multiple scenarios and boundary conditions without duplication
Act as a quality gatekeeper during script development: log, document, and report any defects or unexpected behaviors discovered while building or executing test scripts
Requirements
2+ years of hands-on experience writing automated UI tests (Playwright)
Strong object-oriented programming mindset
Proficiency in JavaScript or TypeScript
Practical experience with the Page Object Model or equivalent structured test architecture
Hands-on experience designing data-driven test frameworks: parameterized test cases, external data sources (JSON, CSV, Excel), and test matrix coverage strategies
Disciplined bug reporting habits: able to write clear, reproducible defect reports with steps to reproduce, expected vs. actual results, severity classification, and attached evidence (screenshots, or Playwright traces)
Familiarity with Git-based workflows: branching, merge requests, and CI/CD pipelines (GitLab preferred)
Ability to reverse-engineer complex UI flows, inspect DOM selectors, and handle timing/state challenges without relying on fixed sleeps
Nice to have
Experience testing Oracle EBS, OAF-based UIs, or other enterprise ERP systems
Exposure to AI-assisted development tools (Claude Code, GitHub Copilot, or similar)
Familiarity with Playwright MCP or Model Context Protocol tooling
Experience with test data management strategies in complex transactional systems
Background in finance, procurement, or ERP domain knowledge