Vidit Agarwal

SDET / QA Automation Engineer

I break things on purpose — then build the automation that stops them breaking again.

Work

End-to-End Booking Flow Automation

✓ PASS
6 wks6 modules automated, 0 → full regression coverage

Problem — A multi-step booking flow (login via OTP, slot selection, cart, payment, summary) had no automated regression coverage, making every release a manual re-check.

Approach — Built a Python + Playwright framework using the Page Object Model with a shared BasePage, isolated fixtures per logged-in state, and dedicated handling for the payment gateway's iframe/popup behavior.

PythonPlaywrightPOMPytestPayment Gateway
GitHub →

API Test Suite — Public REST API

✓ PASS
2 wks60+ cases, wired into CI on every PR

Problem — Needed a repeatable way to validate CRUD behavior and edge cases for a REST API without relying on manual Postman runs before every release.

Approach — Started manual exploration in Postman (environments, chained requests, Tests tab), then rebuilt the coverage in Python using requests + pytest, with one clearly-named test per behavior.

PostmanPythonRequestsPytestGitHub Actions
GitHub →

Security Testing — OWASP Top 10 Case Studies

● RUNNING
3 wksIDOR, auth flaws, and business-logic issues found in practice apps

Problem — Wanted hands-on security testing skill beyond theory — specifically the vulnerability classes most relevant to booking and payment systems.

Approach — Worked through DVWA and Juice Shop with Burp Suite Community Edition, prioritizing high-impact classes first: IDOR, broken access control, and business logic flaws, before moving to JWT and API-specific issues.

Burp SuiteDVWAJuice ShopOWASP Top 10

Skills

Automation

  • Python
  • Playwright
  • Selenium (basics)
  • POM

API Testing

  • Postman
  • Requests
  • Pytest
  • REST

Security

  • Burp Suite
  • OWASP Top 10
  • DVWA
  • Juice Shop

Tooling

  • Git/GitHub
  • GitHub Actions
  • Allure
  • k6

Quality isn't a phase — it's the design constraint

I'm a QA engineer moving toward SDET work, building real automation against real systems rather than tutorials — booking flows, payment integrations, and the security issues that hide in business logic. I like understanding *why* a pattern works before I use it, and I'd rather ship one well-tested case study than five untested demos.

Let's talk testing

Open to SDET and QA automation roles. The fastest way to reach me is email.

viditagarwal79@gmail.com