Manual & Automation Tester (2–4 Years) – Noida

Company:

Location:

Employment Type:

About the Role:

Automation Tester

What You'll Do

• Own the

  test automation strategy

  across web/API/mobile; drive shift-left testing with developers.
• Design and maintain

  robust automation frameworks

  (e.g., Playwright/Cypress/Selenium/Appium) with clean architecture and reusable utilities.
• Build

  API automation

  (REST/GraphQL) including contract tests, schema validation, and negative cases.
• Integrate and stabilize suites in

  CI/CD

  (GitHub Actions/GitLab), including parallelization, flaky-test control, and test artifacts (videos, screenshots, logs).
• Implement

  test data management

  : deterministic fixtures, environment switches, and stubs/mocks for external services.
• Pair with developers on PR checks, code reviews for testability, and triage of intermittent failures.
• Maintain

  living documentation

  : test plans, coverage maps, and runbooks for failures.

Must-Have Skills:

• 2–4 years

  in QA automation for web and/or mobile products.
• Hands-on with at least one

  UI automation tool

  : Playwright / Cypress / Selenium (and Appium for mobile, if applicable).
• Strong

  API testing & automation

  : Postman/Newman or REST clients + code-level tests (e.g., pytest + requests, SuperTest, or REST Assured).
• Solid programming in

  JavaScript/TypeScript

  or

  Python

  (framework utilities, page objects/screenplay, helpers, assertions).
• Experience building or extending an

  automation framework

  (page objects/screenplay, layers for drivers, selectors, waits, reporting).
• Comfortable with

  Git

  , branching, PR reviews, and

  CI/CD

  pipelines (set up, cache, matrix, artifacts).
• Clear communication, strong ownership, and the ability to

  debug failures quickly

  across logs, traces, and screenshots.

Tools & Stacks:

• Automation:

  Playwright/Cypress/Selenium; Appium (if mobile)

• Language & Test Runners:

  TypeScript/JavaScript (Playwright/Cypress/Jest), or Python (pytest)

• API:

  Postman/Newman, or code-based tests (pytest + requests / SuperTest)

• CI/CD:

  GitHub Actions / GitLab CI / Jenkins (parallel runs, artifacts, notifications)

• Reporting & Quality Gates:

  Allure/HTML reports, coverage thresholds

• Version Control:

  Git

Key Performance Indicators (KPIs):

• Automation coverage

  of critical flows and services

• Flakiness rate

  and

  mean time to isolate (MTTI)

  for failures

• Build stability

  (pass rate) and

  time to feedback

  in CI

• Regression cycle time

  and escaped defects to production