Posted today · be early
QA Automation | Offshore
Photon
IndiaremotePosted 1 day ago
Skill Required
QA-Automation-EngineerAutomation-TestingSoftware-Test-EngineerQuality-Assurance-EngineerBrowser-TestingOffshore-Quality-AssuranceQA-AutomationQA-AutomatedAutomated-QAQA-Test-AutomationAutomation-QAQuality-Assurance-AutomationQA-And-Test-AutomationAutomated-QA-EngineeringQA-(Automation-and-Manual)QA EngineerautomationPlaywrightanalyticaldebuggingSeleniumCypressTestNGJavaAWSandFulltime
Role overview
Responsibilities
- Automate existing manual test cases (~150, expected to increase) for the eFront web application.
- Build and maintain automation scripts using Puppeteer (preferred) or equivalent UI automation tools.
- Execute automated test suites during upgrades/releases and analyse failures.
- Review, update, and optimize regression scenarios provided by business and platform delivery teams.
- Ensure automation resilience during vendor-driven UI changes.
- Perform cross-browser automation for Edge and Chrome.
- Document automation coverage, results, and defects.
- Collaborate with cross-functional teams (Business Analysts, Platform Delivery, QA leadership).
Requirements
- Strong hands-on experience with UI automation for browser-based applications.
- Expertise with Puppeteer (primary tool), and familiarity with Selenium/Playwright/Cypress.
- Ability to automate manual regression tests without access to backend code.
- Strong understanding of black-box and grey-box testing methodologies.
- Experience working with large enterprise applications.
- Strong analytical, debugging, and communication skills.
Nice to have
- Experience with third-party vendor applications (e.g., eFront).
- Background in financial domain or fund administration.
- Knowledge of Java-based front-end systems.
- Experience working with AWS-hosted platforms.
Additional details
- Application: eFront (third-party financial platform)
- Frontend Technology: Java-based, browser-rendered
- Backend: Vendor-hosted in AWS
- Browsers: Edge (primary), Chrome (secondary)
- Testing Type: Functional UI automation
- Integration Scope: Primarily UI; limited API usage
- Data Interaction: Mostly within eFront; limited external data exchange through flat files
- Originally posted on Himalayas