Before you start installing anything (that is the next chapter), here is a map of every tool you will learn in this path. Knowing what each tool does and why you need it helps you see the big picture.
| Tool | What It Does | Where You Learn It |
|---|---|---|
| Java (JDK 17) | Programming language — write all test code in Java | Chapters 3–6 |
| IntelliJ IDEA | IDE — write, run, and debug Java code | Chapter 2 |
| Maven | Build tool — manage dependencies, compile, run tests | Chapter 2, 16 |
| Selenium WebDriver | Browser automation — control Chrome, Firefox, Edge programmatically | Chapters 8–10 |
| TestNG | Test framework — organize tests, run in parallel, generate reports | Chapter 11 |
| Cucumber | BDD framework — write tests in plain English (Gherkin) | Chapter 12 |
| Page Object Model | Design pattern — organize test code for maintainability | Chapter 13 |
| Git & GitHub | Version control — track changes, collaborate with team | Chapter 7 |
| Jenkins | CI/CD server — run tests automatically on every code push | Chapter 17 |
| Allure | Reporting — generate visual, shareable test reports | Chapter 18 |
You write test code in Java ──→ using IntelliJ IDEA
↓
Maven manages dependencies (Selenium, TestNG JARs)
↓
Selenium WebDriver controls the browser
↓
TestNG runs the tests and reports pass/fail
↓
Git tracks your code changes
↓
Jenkins triggers tests automatically on every push
↓
Allure generates beautiful reports for your teamEvery tool in this chain is industry-standard. When you list these on your resume — Java, Selenium, TestNG, Maven, Git, Jenkins, Allure — you are matching 90% of SDET job descriptions.
Maven uses a file called pom.xml to manage your project. You will create this in Chapter 2. Here is a preview — every dependency your test project needs:
<dependencies>
<!-- Selenium — browser automation -->
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-java</artifactId>
<version>4.20.0</version>
</dependency>
<!-- TestNG — test framework -->
<dependency>
<groupId>org.testng</groupId>
<artifactId>testng</artifactId>
<version>7.10.2</version>
</dependency>
<!-- RestAssured — API testing -->
<dependency>
<groupId>io.rest-assured</groupId>
<artifactId>rest-assured</artifactId>
<version>5.4.0</version>
</dependency>
</dependencies>Maven reads this file, downloads all the libraries automatically, and makes them available in your project. No manual JAR downloads. No classpath headaches.
Automation testing is one of the fastest-growing career paths in Indian IT. Here is a realistic salary progression:
| Experience | Role | Salary Range (India) |
|---|---|---|
| 0-2 years | Junior QA / Manual Tester | 3-6 LPA |
| 2-4 years | Automation Test Engineer | 6-12 LPA |
| 4-7 years | Senior SDET / Lead | 12-22 LPA |
| 7+ years | Test Architect / QA Manager | 20-35+ LPA |
The jump from manual tester (3-6 LPA) to automation engineer (6-12 LPA) is the highest ROI career move in QA. This path gives you everything you need to make that jump.
Q: What tools have you used for test automation?
A: I use Java as the programming language, Selenium WebDriver for browser automation, and TestNG as the test framework. Maven manages project dependencies and builds. I follow the Page Object Model design pattern for maintainability. For CI/CD, I use Jenkins to trigger tests on every code push, and Allure for test reporting. Git and GitHub handle version control.
Q: Describe your test automation framework.
A: My framework is built with Java, Selenium WebDriver, and TestNG. It follows the Page Object Model pattern where each web page has a corresponding Java class. Test data is externalized in Excel or JSON files for data-driven testing. Maven handles the build. Tests run on Jenkins with parallel execution configured in testng.xml. Allure generates HTML reports with screenshots on failure.
Exercise 1: Draw a diagram (on paper or in any tool) showing how the tools in this path connect. Start with "Java Code" and end with "Test Report." Include all tools mentioned in this lesson.
Exercise 2: Search for "SDET interview questions" on Google. Find 5 questions that are about the tools listed in this lesson (not about testing theory). Write down the questions — you will learn the answers as you progress through this path.
Answer all 10 questions, then submit to see your score.
1. What programming language does this path use for test automation?
2. What is the main reason Java dominates the QA job market in India?
3. The Arrange-Act-Assert pattern means:
4. According to the testing pyramid, which tests should make up the largest portion of your suite?
5. Which tool controls the browser in a Selenium test?
6. When should you NOT automate a test?
7. What does Maven do in a test automation project?
8. What is the biggest mistake people make when learning automation?
9. Smoke testing is:
10. What role does TestNG play in the automation toolkit?