Why Every QA Tester Should Learn Selenium in 2026

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.testng.Assert;
import org.testng.annotations.*;

public class LoginTest {
    private WebDriver driver;

    @BeforeMethod
    public void setUp() {
        driver = new ChromeDriver();   // Selenium Manager resolves the driver
        driver.get("https://www.saucedemo.com/");
    }

    @Test(groups = {"smoke"})
    public void validLoginOpensInventory() {
        driver.findElement(By.id("user-name")).sendKeys("standard_user");
        driver.findElement(By.id("password")).sendKeys("secret_sauce");
        driver.findElement(By.id("login-button")).click();
        Assert.assertTrue(driver.getCurrentUrl().contains("inventory"));
    }

    @AfterMethod
    public void tearDown() {
        driver.quit();
    }
}

<!DOCTYPE suite SYSTEM "https://testng.org/testng-1.0.dtd">
<suite name="Smoke" parallel="methods" thread-count="3">
  <test name="SmokeTests">
    <groups>
      <run><include name="smoke"/></run>
    </groups>
    <classes>
      <class name="LoginTest"/>
    </classes>
  </test>
</suite>

@DataProvider(name = "logins")
public Object[][] logins() {
    return new Object[][] {
        {"standard_user", "secret_sauce", true},
        {"locked_out_user", "secret_sauce", false},
        {"standard_user", "wrong_password", false},
        {"", "secret_sauce", false},
    };
}

@Test(dataProvider = "logins", groups = {"regression"})
public void loginBehaviour(String user, String pass, boolean shouldPass) {
    driver.findElement(By.id("user-name")).sendKeys(user);
    driver.findElement(By.id("password")).sendKeys(pass);
    driver.findElement(By.id("login-button")).click();
    Assert.assertEquals(driver.getCurrentUrl().contains("inventory"), shouldPass);
}

# docker-compose.yml — Selenium Grid 4 hub with two browser nodes
services:
  selenium-hub:
    image: selenium/hub:latest
    ports: ["4442:4442", "4443:4443", "4444:4444"]
  chrome:
    image: selenium/node-chrome:latest
    shm_size: 2gb
    depends_on: [selenium-hub]
    environment:
      SE_EVENT_BUS_HOST: selenium-hub
      SE_EVENT_BUS_PUBLISH_PORT: 4442
      SE_EVENT_BUS_SUBSCRIBE_PORT: 4443
  firefox:
    image: selenium/node-firefox:latest
    shm_size: 2gb
    depends_on: [selenium-hub]
    environment:
      SE_EVENT_BUS_HOST: selenium-hub
      SE_EVENT_BUS_PUBLISH_PORT: 4442
      SE_EVENT_BUS_SUBSCRIBE_PORT: 4443

pipeline {
    agent any
    triggers { cron('H 1 * * *') }          // nightly
    stages {
        stage('Checkout') { steps { checkout scm } }
        stage('Regression') {
            steps {
                sh 'mvn -B test -DsuiteXmlFile=testng-regression.xml -Dgrid.url=http://selenium-hub:4444'
            }
        }
    }
    post {
        always { junit 'target/surefire-reports/*.xml' }
    }
}

import org.openqa.selenium.chrome.ChromeOptions;
import org.openqa.selenium.remote.RemoteWebDriver;
import java.net.URL;

String gridUrl = System.getProperty("grid.url", "http://localhost:4444");
WebDriver driver = new RemoteWebDriver(new URL(gridUrl), new ChromeOptions());

Week 1: Java basics for testers (classes, methods, lists)
Week 2: Selenium WebDriver in Java; locators; waits
Week 3: TestNG annotations, groups, testng.xml
Week 4: DataProvider for data-driven tests
Week 5: Selenium Grid in Docker; parallel runs
Week 6: Jenkins job running the suite; read reports

Project: Demo store regression suite (Java + TestNG)
- 15 tests across login, cart and checkout
- smoke and regression groups
- DataProvider for login combinations
- Runs on Grid (Chrome + Firefox) in parallel
- Jenkins or GitHub Actions job with published reports

Ask when you join a QA automation team:
1. Where is the suite, and how do I run it locally?
2. Which groups or suites run on which trigger?
3. Where are reports published?
4. How do we handle known flaky tests?
5. What are the coding conventions for tests?