Skip to main content
ashish.kumar

Uses

Not just a tag list — the stack I actually reach for, and why. See Skills for the full inventory.

UI & mobile automation

Playwright is what I reach for first on new projects; Selenium and Appium still earn their keep on legacy suites and cross-browser/mobile coverage.

  • Playwright
  • Selenium
  • Cypress
  • Appium
  • TestNG
  • Cucumber

API & performance

REST Assured plus SQL-level checks for backend data consistency, JMeter when I need load numbers, not just pass/fail.

  • REST Assured
  • JMeter

AI-assisted workflow

Cursor and Claude Code for first-draft test scaffolding and debugging flaky failures fast; GitHub Copilot inline; ChatGPT for one-off research. None of these replace deciding what actually needs coverage — that part stays manual. I also built an MCP server for this portfolio — a concrete example, not just a tools list.

  • Cursor
  • Claude Code
  • GitHub Copilot
  • MCP Server
  • ChatGPT

CI/CD & infra

GitHub Actions for anything greenfield, Jenkins where it's already entrenched, Docker to keep environments reproducible, AWS for the infra underneath.

  • GitHub Actions
  • Jenkins
  • Docker
  • AWS

Data & observability

MySQL/MongoDB for the systems under test, Redis and Sentry mostly from side-project infra work.

  • MySQL
  • MongoDB
  • Redis
  • Sentry

Process

Git and Bitbucket for version control, Jira for tracking, TestRail when a project needs formal test-case management.

  • Git
  • Bitbucket
  • Jira
  • TestRail