What this class covered
- What the next 90 days cover, and what happens after them
- The roadmap: JavaScript, then TypeScript, then Playwright, then CI/CD and AI
- The progress dashboard on app.thetestingacademy.com, and the daily entry
- SDET Club: the private batch space, the public groups, and the mobile app
- Notes, recordings, and the required access form
- The three GitHub repositories you will build
- Branding: posting on LinkedIn and Medium from day one
- Why most people do not finish, and the rule for when life gets in the way
- Four working rules for the batch
- Editors and AI coding tools: VS Code, and no AI for the first stretch
- The live schedule, the daily threads, and the day-one tasks
What the 90 days are
This is the fifth run of the batch, and it covers JavaScript, TypeScript, Playwright and AI over roughly 90 days. The course does not stop there: extra classes, mock interviews, the SDET masterclass, AI sessions, and more exercises and tests continue afterwards. Two things are new for this batch: free Claude certifications, with a repeat lecture planned, and an agentic QA module using LangChain to drive Playwright runs, which was previously only in the AI Tester Blueprint batch.
Pramod is the only instructor and mentor. Deepak handles operations and access, and Niti helps with queries.
The framing for the whole batch: you do the learning, the mentor guides it. Every keyword that comes up in class (hoisting, let, shadow DOM, SVG, agent factory) is something to go and research yourself afterwards. That habit is what separates the people who finish.
The roadmap
The order is fixed, because each stage depends on the one before it. You cannot learn TypeScript without JavaScript, and you cannot debug Playwright in a language you cannot read.
A spreadsheet with every topic in the roadmap is shared with the batch. Keep the roadmap somewhere you see it daily.
Where everything lives
The progress dashboard. Create a free account on app.thetestingacademy.com. Under My Progress, use "add today's learning" to record what you did each day; the entries show up on a calendar. A daily entry is mandatory, because progress is tracked from it.
SDET Club is the community, hosted on Circle, with apps for Android and iOS. The 4x batch space is private: that is where tasks are posted and where you can ask as many questions as you like. The public groups hold resources, discussions, and a jobs and referrals group where alumni share interview questions and referrals. Invites go out by email from contact@thetestingacademy.com after the kickoff, so check it has not landed in spam. A laptop is recommended over the phone app.
Notes for the whole 100 days live in a single Eraser canvas, so drawings made in class sit beside the text. Recordings are under My Courses, and both links are at the top of the batch space.
What is the difference between app.thetestingacademy.com and SDET Club? SDET Club is for communication: tasks, doubts, discussion. app.thetestingacademy.com is for learning and tests.
The required access form removes access as well as granting it. If you are missing SDET Club or a bonus course, fill it in and the team calls you. If you already have access, do not fill it: there is an automated process behind the form, and it can take away access you already hold. For anything else, the class support WhatsApp link was shared in the class chat.
The three repositories
Every student builds three public repositories on GitHub:
- JavaScript and TypeScript: roughly 200 to 250 exercises.
- Playwright: every Playwright concept covered in class.
- The advanced Playwright framework, with AI, Cucumber and API testing.
Show them in interviews. A repository is the one claim on a resume that an interviewer can open and check.
Branding from day one
Learning Playwright alone does not make you stand out. The recommendation is to post on LinkedIn, and on Medium if you can, from the first day: take a 100-day challenge and post what you learned. A guide on how to post is being shared with the batch. Previous students have posted their projects and certifications, and that visibility is part of how people get noticed and hired.
Why people do not finish
In the instructor's experience, roughly three in ten students complete the course and its exercises. The reason is almost never the roadmap, the practice, or a fear of coding. It is that life keeps producing a crisis: work pressure, a hotfix, illness, family. Those never stop, so the rule is simple: keep learning anyway. Consistency is the whole method.
Two supporting points came with it. Cut short-video and social media time to under 30 minutes a day; an Android launcher such as Niagara Launcher, which makes the phone deliberately plain, was the instructor's own fix. And sort your finances before a career move: an emergency fund of several months of expenses, plus health and term cover, because money pressure is a common reason people drop out. The Psychology of Money was the recommended book, and there is a books section on the platform.
Four working rules
On rule three, the instructor's own examples: he cleared an interview at Wingify with perhaps 30 to 40 percent of the API knowledge he thought he needed, and was rejected by BrowserStack the first time, then hired there when he tried again six months later. The plan is to start giving interviews after about a month and a half to two months, because interviews are how you find out where you actually stand.
Editors and AI coding tools
Everyone uses VS Code. Install it before the next class.
No AI coding tools for the first month and a half to two months, until JavaScript and TypeScript are solid. The instructor will not use them in class during that stretch either. After that, the options depend on what you already have access to:
| If you have | Use |
|---|---|
| Cursor, Windsurf or Claude Code, paid or through work | that, when the time comes |
| GitHub Copilot through work, or its individual plan | Copilot |
| A personal laptop and a small budget | Command Code or OpenCode, both of which have low-cost plans; Cursor also has a lower-priced plan for India |
All of it is optional. Do not buy anything now. If your employer already provides a tool, use that. Local models through Ollama were not recommended unless you have 16 GB of RAM or more. And one line worth remembering: there is no genuinely free AI tool; if something is free, you are the product.
Tasks and announcements
- Live classes: Monday, Wednesday and Friday. This class ran 7 to 8 AM IST. There are also optional extra AI sessions every two weeks, usually on a Tuesday or Friday evening.
- Create a GitHub account. Mandatory.
- Create a free account on app.thetestingacademy.com, and add a daily entry under My Progress.
- Create a Medium account, and get your LinkedIn profile ready.
- Install VS Code.
- Introduce yourself in the private batch space: who you are, why you are here, whether you are working, your email and your GitHub profile.
- Three threads to use: a daily doubt thread (dated, "PW4X doubt"), a GitHub repositories thread where everyone posts their repo links, and a certifications thread for screenshots of certifications you complete. A certification list is being shared.
- Next class: how to use AI for QA, and installing Playwright.
Day-one checklist. GitHub account, app.thetestingacademy.com account with today's entry added, Medium account, VS Code installed, and your introduction posted in the batch space with your GitHub profile.