track-01 --manual-to-automation

Manual → Automation Testing

The most in-demand conversion in QA today — here's exactly how it's structured, phase by phase.

why --this-track

Why this conversion, specifically

Manual testing skills don't disappear when you automate — they become the judgment that makes your automation actually useful. This track is built so your existing testing instincts (what to test, edge cases, risk areas) carry forward, while you layer real programming and tooling skills on top.

PHASE 01 · ~2–3 WEEKS

Programming Foundations

Core Java from scratch: variables, OOP (classes, inheritance, polymorphism), collections (List/Map/Set), exception handling, and the file-handling basics you'll actually use in automation. No prior coding background assumed.

PHASE 02 · ~3–4 WEEKS

Automation Tooling

Selenium WebDriver — locator strategies, explicit/implicit waits, handling dynamic elements, frames, alerts, and multi-window scenarios. TestNG for test structuring, annotations, assertions, and parallel execution.

PHASE 03 · ~2 WEEKS

BDD & Reporting

Cucumber and Gherkin syntax for behavior-driven scenarios that non-technical stakeholders can read. Extent/Allure reporting so your test runs produce evidence anyone can review.

PHASE 04 · ~3–4 WEEKS

CI/CD & Framework Design

Maven for dependency/build management, Jenkins and GitLab CI for running your suite automatically. Page Object Model and a hybrid framework you design and build yourself — this becomes your portfolio piece.

PHASE 05 · ONGOING

Interview Readiness

Mock technical rounds specific to automation roles, resume repositioning from "Manual Tester" to "Automation Engineer," and a final review of your framework project before you start applying.

outcome --expected

What you'll walk away with

🎯 READY WHEN YOU ARE

Start with a 1:1 session, not a guess.

Your first session is a skill assessment — we figure out exactly where you stand on this roadmap and what your specific plan looks like, before committing to anything bigger.