What Is Software Testing (Manual vs Automation)

Why this matters

Broken apps lose trust. Banks, ecommerce and SaaS teams in India hire testers and SDETs who can explain bugs clearly and automate the boring checks. You do not start with AI — you start with what “pass” and “fail” mean.

What you will learn

You will learn the goal of testing, the difference between manual and automation, when each shines, and a tiny map of the rest of this course (cases → Playwright → AI-assisted cases).

How to do it

We use a fictional “LearnKart” student login page as the running example. No paid tool licences are required for Volume 1.

Steps (do these in order)

1. Step 1 — Define pass and fail. Pass: agreed behaviour happened. Fail: it did not — or an error was unclear. Write both for “valid login”.
2. Step 2 — Manual first. Click through login with valid, wrong password, and empty fields. Note what you saw. That is manual testing.
3. Step 3 — Where automation helps. Same three checks every day after each deploy — humans get bored; scripts do not.
4. Step 4 — Where humans still win. Usability, confusing copy, “this feels wrong on mobile” — still manual / exploratory.
5. Step 5 — Course map. Ch2 cases & bugs → Ch3 black/white box → Ch4 Playwright → Ch5 locators → Ch6 page objects. AI chapters come after Volume 1.

Practice

• Write three manual checks for a “Forgot password” link on LearnKart.
• In two sentences, explain to a friend when you would automate vs test by hand.