Open to opportunities

Hi, I'm Ashakiran Jyoti

QA Automation Engineer — Playwright · Manual Testing · Agile

I've spent the last 2+ years breaking things on purpose — testing and automating enterprise systems that real people depend on. My work on AMRUT 2.0 (Government of India water infrastructure) and Inventory Management System (IMS) taught me that good QA isn't just scripts — it's knowing what to test and why. I write automation in JavaScript (Playwright) at work and TypeScript in personal projects.

Playwright · JS & TS (v1.40+) Page Object Model Manual Testing Agile · Scrum API Testing Git Govt. of India Project AI-Assisted Workflow
Projects Experience GitHub Contact Resume
300+
Test Cases Written
Across 2 projects — manual suites covering all STLC phases
160+
Automated Scripts
Playwright JS — login, RBAC, stock, SCADA, API, reports
15+
Critical Bugs Caught
RBAC security flaw & data integrity bug — both blocked release
70%
Regression Efficiency
Helped reduce regression testing effort through automation
// about

QA Automation Engineer — Manual + Automation

I'm a QA Automation Engineer who genuinely enjoys finding bugs before users do. Over 2+ years, I've learned that the best QA happens when manual instinct and automation work together — not separately. I code in JavaScript at work and push myself with TypeScript in personal projects.

My most meaningful work has been on AMRUT 2.0 — a live Government of India SCADA dashboard monitoring water supply across Indian cities — and an Inventory Management System. On both, I didn't just run test cases. I caught a security flaw in RBAC, blocked a data integrity bug from reaching production, and designed a real-time testing protocol with the dev team from scratch.

I use AI tools (Claude, ChatGPT, GitHub Copilot, Cursor, Windsurf) the way a senior engineer would — for the boring parts, not the thinking parts. One rule I never break: no real credentials, IPs, or government data ever touches an AI prompt.

Manual Testing STLC · Agile · Scrum Bug Tracking Playwright · JS & TS · v1.40+ Page Object Model API Testing Git AI-Assisted Workflow
// skills

Testing & Automation Stack

What I use at work and what I'm building independently

Test Automation
Playwright (JavaScript) · v1.40+ Playwright (TypeScript) Page Object Model Data-Driven Testing Custom Fixtures HTML Reports Git Cross-Browser Testing
Manual Testing
Test Case Design Functional Testing Regression Testing Exploratory Testing Boundary Value Analysis Equivalence Partitioning Smoke & Sanity Bug Lifecycle · STLC Agile · Scrum
API Testing
Playwright Request Context REST APIs Postman CRUD Validation Auth Testing Schema Validation Multi-env Config Negative Testing
QA Concepts
Test Planning & Strategy RBAC Testing Security Testing Integration Testing Real-time Data Testing UAT Sprint QA Summaries
Tools & Platforms
VS Code Git · GitHub Node.js · npm Playwright Trace Viewer MS SQL Server MySQL Excel (Test Docs)
AI in QA Workflow
GitHub Copilot Cursor AI Windsurf Claude · ChatGPT Edge Case Brainstorming Test Scaffolding Prompt Engineering Sanitized Prompting
// experience

Work Experience

Manual and automation — both, simultaneously, every sprint

Current Role
Modern Communication Technology (MCOM)
QA Automation Engineer — IMS & AMRUT 2.0
June 2024 – Present · Pune, Maharashtra
Manual Testing
  • Designed 300+ test cases from scratch — not templates, actual sprint-by-sprint thinking across AMRUT 2.0 and IMS
  • Ran full testing cycles — functional, regression, smoke, RBAC, BVA, exploratory — every sprint, not just release time
  • Caught a RBAC security flaw that let restricted users trigger live SCADA control buttons — filed, escalated, verified fix
  • Found a data integrity bug at boundary value (quantity = available + 1) — stopped it from reaching production
  • Built a real-time SCADA test protocol with the developer — inserted known sensor values so assertions could actually pass
  • Every bug report I file has Steps, Expected, Actual, Severity, and a screenshot — developers don't have to guess
  • Use AI for edge case brainstorming — but validate every suggestion before it becomes a test case
  • Sprint QA summaries are mine — pass/fail counts, open bugs, risk areas, done every single sprint
Playwright Automation (JS)
  • Built and maintained 160+ Playwright scripts in JavaScript using Page Object Model — covering both IMS and AMRUT 2.0
  • Automated login flows, stock lifecycle, SCADA dashboard, RBAC, report exports, and AJAX cascade dropdowns
  • Solved AJAX cascade challenge using waitForResponse — intercepted API call before asserting child dropdown
  • Diagnosed and fixed flaky SCADA tests — used Playwright trace viewer + Cursor AI to identify race condition
  • Maintained automation scripts in Git — tracked changes, collaborated with team members
  • Helped reduce regression testing effort through comprehensive automation coverage
AI Tools — Where I Used Them
  • GitHub Copilot — POM class boilerplate and assertion blocks; I validate selectors and logic
  • Cursor AI — root cause analysis for flaky SCADA tests; trace-based debugging with AI-assisted explanation
  • Windsurf — multi-file JS→TS migrations in personal projects; reviewed every change before accepting
  • ~40% faster authoring on boilerplate; all test strategy and edge case design decisions are mine
Playwright · JSPage Object Model Manual TestingAgile · Scrum GitMS SQL ServerMySQL GitHub CopilotCursor AIWindsurf
IT JOBXS
Junior QA Engineer
October 2023 – May 2024 · Pune, Maharashtra
  • Tested bot detection, spam prevention, and user authentication — security-focused functional testing
  • Validated Google reCAPTCHA integration end-to-end across multiple user scenarios
  • Wrote test cases, reported defects, and collaborated with developers on fix verification
Manual TestingSecurity TestingFunctional Testing
// testing depth

How Manual & Automation Work Together

Same sprint, same feature, both happening in parallel

Manual — Sprint Flow

From User Story to Executed Test

Every sprint I receive User Stories with Acceptance Criteria. I break them into test cases (happy path + negatives + edge cases), execute on staging, file bugs, retest fixes, and summarise results.

  • AMRUT example: Zone Board Alert — 1 US → 8 test cases (5 ACs + AI-brainstormed edges)
  • IMS example: Inward Stock Form — 1 US → 11 test cases including AJAX empty-array state
  • Security catch: View-Only users could trigger SCADA control buttons — RBAC testing
  • Data integrity catch: Invalid stock at quantity = available + 1 — boundary value analysis
  • Bug reports: Title · Steps · Expected · Actual · Environment · Severity + screenshot
Automation — Same Sprint

Scripts Written Alongside Manual Tests

Automation isn't a separate phase — I write scripts for the same features I'm testing manually, within the same sprint. Work automation is in JavaScript; personal framework projects are TypeScript.

  • AJAX cascade fix: waitForResponse to intercept API call before asserting dropdown
  • Real-time SCADA: Live sensor data every 15s → designed insert-known-value test protocol with developer
  • Flaky test fix: Trace viewer + Cursor AI to identify race condition — resolved to zero failures
  • Personal TS projects: DemoBlaze (Allure + GitHub Pages), SauceDemo (3-browser), ReqRes API
  • Version control: All automation scripts maintained in Git
// ai workflow

AI Tools in My QA Process

Specific tools, specific moments — decisions always mine

I use AI at specific, bounded moments — edge case brainstorming, boilerplate scaffolding, debugging, and refactoring. Test strategy, execution, and sign-off are always mine. Hard rule: no real server IPs, credentials, DB values, or government data goes into any AI tool. All prompts are sanitized generic descriptions.

GitHub Copilot
VS Code · Daily driver

Handles boilerplate so I focus on selector accuracy, test logic, and edge case coverage.

  • POM class scaffolding — locator maps for complex forms
  • Test structure — describe/test blocks, beforeEach hooks
  • Assertion blocks — bulk field validations drafted, then refined by me
~40% faster boilerplate
✦
Cursor AI
Debugging · Code chat

Used when a test failure needs deep investigation — trace-based debugging with AI-assisted explanation.

  • Flaky SCADA tests — race condition traced and fixed
  • Playwright errors — async/timeout failures decoded faster
  • Coverage gaps — AI scans test logic for missed paths
Faster root cause analysis
🌊
Windsurf
Agentic · Multi-file

Used for large-scope refactoring in personal TypeScript projects — reviews across multiple files.

  • JS → TS migration — type annotations added, logic intact
  • Interface generation — TS interfaces from JSON test data shapes
  • Import fixes — multi-file path updates in a single session
Multi-file refactoring
My Workflow — Where AI Plugs In
1Read User Story
→
2Design Test Cases
→
3AI: Edge Case Brainstorm
→
4Execute Manual Tests
→
5AI: Scaffold Automation
→
6AI: Debug Failures
→
7Commit → Push → Share
// projects

Work Projects & Personal Frameworks

JavaScript for work · TypeScript for personal skill building

Work Projects — JavaScript

AMRUT 2.0 — SCADA Dashboard

Govt. of India · Water Infrastructure

8 modules tested on a live Government of India dashboard monitoring 50+ water pumping stations — real sensor data every 15–60s, remote controls, role-based access.

150+ manual test cases · 50+ automated Playwright scripts · Found RBAC security bug · Designed real-time test protocol with developer.

Playwright JSPOMMS SQL ServerRBAC TestingCursor AI
Government of India

Inventory Management System

Internal Enterprise Application

7 modules tested on an internal IMS — inward/outward stock, shortage detection, 1000+ product categories (3-level hierarchy), PDF/Excel exports.

150+ manual test cases · 60+ automated scripts · Critical data integrity catch blocked release · Solved AJAX cascade with waitForResponse.

Playwright JSPOMMySQLBVAGitHub Copilot
Critical bug blocked release

Site Track System

Field Operations · Internal Tool

Role-based field operations — Sites → Tubewells → LCS (3-level hierarchy), media uploads, audit trails, compliance workflows.

60+ manual test cases · 60+ automated scripts covering CRUD across all hierarchy levels, upload edge cases, access control end-to-end.

Playwright JSPOMCRUD TestingSecurity TestingGitHub Copilot
GitHub
Personal Frameworks — TypeScript

DemoBlaze — E2E TS Framework

TypeScript · Allure · GitHub Pages

JS→TS migration practice — typed POM classes, interfaces, explicit return types. Allure reports auto-published to GitHub Pages on push.

Login (multi-role), products, cart, checkout — smoke + regression tagged suites, externalized test data.

Playwright TSPOMAllureGitHub ActionsTagged Suites
GitHub Allure Report

SauceDemo — Cross-Browser TS

TypeScript · Chromium · Firefox · WebKit

Cross-browser test framework — typed page objects, externalized test data (users.json, products.json), screenshot + video on failure.

Auth, product management, cart, full checkout — runs on all 3 browsers.

Playwright TSPOMCross-browserGitHub ActionsData-driven
GitHub Allure Report

ReqRes REST API Framework

TypeScript · Multi-env · API Testing

Typed API test framework — typed client layer, DEV/QA environment config via env var, reusable assertion helpers.

Full CRUD coverage + negatives: GET (pagination), POST (create + missing fields), PUT (update), DELETE (valid + invalid IDs).

Playwright RequestTypeScriptMulti-envSchema ValidationGitHub Actions
GitHub Allure Report
All on GitHub
// education

Academic Background

Bachelor of Technology (B.Tech)
Computer Science & Engineering
Dr. Babasaheb Ambedkar Technological University
Lonere, Maharashtra · Graduated 2023
CGPA: 8.33 / 10
// contact

Get In Touch

Open to QA Automation Engineer & SDET roles

Location
Pune, Maharashtra, India

Looking for QA Automation Engineer or SDET roles — I bring Playwright automation (JS + TS), hands-on manual testing, Agile experience, and an AI-augmented workflow, all delivered simultaneously on real enterprise projects.

QA Automation Engineer SDET QA Engineer