QA AUTOMATION
Automation in Java: Selenium + RestAssured — build a real test framework
This course is designed to help you move from “I know automation basics” to
“I have a strong portfolio framework with UI + API tests, clean structure, and CI-ready runs.”
We focus on practical, job-ready automation using Java Core, Selenium, and RestAssured.
Best for
QA with fundamentals, QA Advance grads, manual → automation
Outcome
UI + API automation portfolio + interview confidence
Duration
6–10 weeks (flexible pace)
Support
Code reviews + mentor feedback
Tip: If you’re not sure you’re ready for automation yet, start with QA Basic or QA Advance first.
What you will build
- A clean Java automation framework (Maven/Gradle)
- UI tests with Selenium (Page Object Model)
- API tests with RestAssured (auth, payloads, validations)
- Reusable utilities: waits, config, test data, reporting
- Parallel runs + stable test strategy
- CI-ready запуск (GitHub Actions / Jenkins basics)
Portfolio result
GitHub repo + README + UI suite + API suite + reports + CI pipeline
Tech Stack
Language
Java Core (OOP, collections, exceptions)
UI Automation
Selenium WebDriver + Page Object Model
API Automation
RestAssured (requests, assertions, auth)
Test Runner
TestNG or JUnit (you can choose)
Build & Dependencies
Maven (recommended) or Gradle
Reports
Allure / Extent (optional), screenshots on fail
You can customize stack later (Cucumber, Docker, etc.) — first we build a stable foundation.
Curriculum
Step-by-step framework building — from structure to CI.
Module 1 — Java Core for QA Automation
Only what you need to write strong tests.
- OOP basics, classes, methods
- Collections, loops, conditions
- Exceptions + clean code practices
Module 2 — Framework setup
Professional structure from day 1.
- Maven project structure
- Config files (env, browser, baseUrl)
- Test runner setup (TestNG/JUnit)
Module 3 — Selenium UI Automation
Stable UI tests that don’t flake.
- Locators (CSS/XPath) + best practices
- Waits (implicit/explicit) + stability rules
- Page Object Model (POM)
Module 4 — UI test design
What to automate first — and what NOT to automate.
- Critical path automation
- Data-driven tests basics
- Screenshots & logs on failures
Module 5 — RestAssured API Automation
From simple calls to real API suites.
- GET/POST/PUT/DELETE, headers, params
- Auth basics (tokens, bearer, etc.)
- Assertions: status, schema, response body
Module 6 — Combining UI + API
Modern QA: faster tests using APIs where possible.
- Create data via API → validate via UI
- Cleanup strategies
- Layered test approach
Module 7 — Reporting & debugging
Make your tests “team friendly”.
- Allure/Extent (optional)
- Logs + screenshots in reports
- Readable assertions & messages
Module 8 — CI basics
Run tests automatically like real teams.
- GitHub Actions (recommended) or Jenkins intro
- Headless runs
- Artifacts: reports, screenshots
Final Project — Automation Portfolio Framework
A complete project you can show in interviews.
- UI suite (10–20 stable tests)
- API suite (10–25 endpoints tests)
- Config per environment + clean structure
- README + how to run + CI pipeline
FAQ
Do I need to know Java already?
Basic understanding helps, but we cover Java Core essentials that you’ll use in tests.
Do we use Cucumber?
Not in the core program (optional bonus). First we build a stable framework foundation.
Will I learn API + UI together?
Yes. You’ll build both suites and learn how to combine them in smart workflows.
What if my tests are flaky?
We teach stability rules: correct waits, good locators, and reliable test design.
What portfolio will I have at the end?
A GitHub repo with UI + API framework, CI run, reports, and a clean README.
