assert_
glossary ↓ downloads
0 / 41 lessons
from manual tester to automation engineer

You already find the bugs.
Now teach the code to click find them.

A hands-on path into automation with Java and Selenium — the stack that runs enterprise QA. No prior coding assumed; skip ahead if you have some.

Start Learning → What is automation testing?
not sure where to start? 30-second placement check
Have you written code in any language?
Could you read for (String b : browsers) and guess what it does?
Used Git before?
Comfortable in a terminal?
Ever written a CSS selector or XPath?
Start at Suite 00 →
the basics

What is automation testing?

Automation testing is writing code that checks software for you. Instead of a person clicking through an app and comparing what they see against what they expect, a program does it — opening the browser, filling forms, clicking buttons, and verifying results. That verification step, where code confirms "this is what should have happened," is called an assertion. It's the heart of every automated test, and where this course gets its name.

You already do all of this in your head as a manual tester. Automation doesn't replace that judgment — it takes the repetitive parts off your plate so your judgment scales. A regression suite that takes two days by hand can run in ten minutes, on every code change, without getting tired or skipping a step.

manual testing
  • You open the browser and navigate by hand
  • You read the screen and judge pass / fail
  • Great for exploration and new features
  • Slow and tiring to repeat every release
  • Coverage limited by human hours
automation testing
  • Code drives the browser through the flow
  • An assertion decides pass / fail, exactly
  • Great for regression and repeated checks
  • Runs in minutes, on every change
  • Coverage limited only by tests you write
The honest truth: automation isn't "better" than manual testing — it's a different tool. The best QA engineers do both. That judgment is a skill you're already building.
the fundamentals

Six ideas that hold everything up

Every lesson in this course maps back to one of these.

01

Locate

Code can't "see" a button. You point it at elements using locators — IDs, CSS selectors, or XPath.

02

Act

Once located, you drive the element: click it, type into it, select from it.

03

Assert

Check reality against expectation. Match: pass. Mismatch: fail loudly.

04

Wait

Pages load asynchronously. Waiting for the right moment is the difference between flaky and reliable.

05

Structure

Patterns like the Page Object Model keep suites readable and maintainable.

06

Run & report

Frameworks run tests on every commit via CI and produce reports the team trusts.

the course

The test suite

Click a suite to see its lessons. Your progress saves in this browser — clearing site data resets it. Accounts with cross-device sync are on the roadmap. Finish all 41 items and your certificate unlocks. reset all progress

○the automation roi test8 min read○what not to automate7 min read○your unfair advantage6 min read⚡suite test — 6 questionspass to merge
○set up your environment (windows)30 min hands-on○git basics — version control for testers15 min○running tests from the terminal12 min⚡suite test — 6 questionspass to merge
○values & variables12 min○conditionals & loops14 min○methods — reusable steps12 min○collections — test data in bulk12 min○intro to oop — why frameworks look the way they do14 min⚡suite test — 7 questionspass to merge
○how a page is built — the dom12 min○css selectors15 min○xpath — when css isn't enough15 min○locator strategy — the practice lesson18 min hands-on⚡suite test — 7 questionspass to merge
○your first selenium script15 min hands-on○finding & acting on elements18 min○smart waits — the flakiness cure15 min○the page object model20 min⚡suite test — 7 questionspass to merge
○structuring a test class15 min○data-driven tests15 min○fixtures, tags & running subsets12 min○reports & failure evidence14 min⚡suite test — 7 questionspass to merge
○rest in 15 minutes15 min○your first api test — rest assured15 min○chaining requests — real api flows15 min⚡suite test — 6 questionspass to merge
○designing a framework15 min○ci — tests on every push18 min○headless & parallel — speed14 min⚡suite test — 6 questionspass to merge
○the capstone brief5 min read○build it — the milestone plan6–10 hrs project○ship & show — portfolio and interviews90 min⚡suite test — 5 questionspass to merge
about

Who built this

assert_ is built by Gokulakrishnan Vasudevan, a software engineer who builds tools and learning platforms for the testing world. It exists for one reason: a belief that professionals grow best by levelling up inside their own domain — not by starting over from zero. The manual→automation jump is usually taught backwards (syntax first, testing instincts never); this course starts from the skills testers already have and builds the engineering on top.

Spotted a mistake, a broken link, or a lesson that didn't land? Tell me on LinkedIn — bug reports from bug hunters are the best kind.