How Uncodemy Trains Students For Automation Tester Roles

// Uncodemy-style Selenium test with a Page Object
// A pattern students build by week 3–4 of the programme.

public class LoginPage {
    private final WebDriver driver;

    @FindBy(id = "email")
    private WebElement emailInput;

    @FindBy(id = "password")
    private WebElement passwordInput;

    @FindBy(css = "button[type='submit']")
    private WebElement loginButton;

    public LoginPage(WebDriver driver) {
        this.driver = driver;
        PageFactory.initElements(driver, this);
    }

    public DashboardPage login(String email, String password) {
        emailInput.sendKeys(email);
        passwordInput.sendKeys(password);
        loginButton.click();
        return new DashboardPage(driver);
    }
}

// Test class
@Test
public void loginWithValidCredentials() {
    LoginPage login = new LoginPage(driver);
    DashboardPage dashboard = login.login(
        "student@example.com", "Password123"
    );
    assertTrue(dashboard.isLoaded());
}

// API testing with RestAssured — a standard module in the programme
// Students validate status, schema and content — not just "did it work?"

@Test
public void createUser_returns201AndEchoesPayload() {
    String body = """
        {
          "name": "Asha Verma",
          "email": "asha@example.com",
          "role": "STUDENT"
        }
        """;

    given()
        .contentType(ContentType.JSON)
        .body(body)
    .when()
        .post("/api/v1/users")
    .then()
        .statusCode(201)
        .body("email", equalTo("asha@example.com"))
        .body("id", notNullValue());

    // Students also chain this with a follow-up GET
    // to verify the user is actually persisted.
}

Automation testing portfolio — what students ship

Project 1 · UI automation
  ☐ Selenium + Page Object Model
  ☐ At least 10 tests across 3 flows
  ☐ Explicit waits, no Thread.sleep
  ☐ README: architecture + how to run

Project 2 · API test suite
  ☐ Postman collection with environments
  ☐ RestAssured suite with assertions
  ☐ Schema validation + negative tests
  ☐ Newman job in CI

Project 3 · Hybrid framework
  ☐ Maven project with clean structure
  ☐ TestNG suite XML
  ☐ Extent Reports with screenshots
  ☐ GitHub Actions pipeline
  ☐ Parallel test execution

Across all three
  ☐ Clean commits, meaningful messages
  ☐ No hardcoded credentials
  ☐ Pinned on GitHub profile
  ☐ Short README per project

# .github/workflows/automation-tests.yml
name: Automation Tests

on: [push, pull_request]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Set up Java 21
        uses: actions/setup-java@v4
        with:
          distribution: temurin
          java-version: "21"

      - name: Run Selenium + RestAssured suite
        run: mvn -B clean test

      - name: Upload Extent Report
        if: always()
        uses: actions/upload-artifact@v4
        with:
          name: extent-report
          path: target/extent-report/

# The point: students finish the programme
# with a live CI pipeline visible on their repo.
# That single line in a README is often what
# gets them the first interview.

Interview prep — final 4 weeks of the programme

Week 1 · Selenium + Java
  ☐ Locators, waits, POM
  ☐ Framework design questions
  ☐ Common Selenium interview questions
  ☐ 2 hands-on live coding sessions

Week 2 · API + SQL
  ☐ REST basics, status codes, auth
  ☐ Postman + RestAssured questions
  ☐ SQL joins, aggregations, subqueries
  ☐ Data validation practice

Week 3 · Behavioural + projects
  ☐ 5-minute project walkthrough
  ☐ "A test is flaky — how do you fix it?"
  ☐ "How would you test X feature?"
  ☐ Resume and LinkedIn polish

Week 4 · Mocks and follow-through
  ☐ Two full mock interviews
  ☐ Feedback and gap-filling
  ☐ Application tracking + follow-ups
  ☐ Confidence building for interviews

Typical automation tester interview flow

Round 1 · Screening (30 min)
  - Background, motivation, basics of testing
  - Sometimes a short SQL or manual QA quiz

Round 2 · Technical — Selenium / Playwright (45–60 min)
  - Write a test for a given scenario
  - Explain POM, waits, framework design
  - Debug a broken test live

Round 3 · Technical — API / SQL (45–60 min)
  - Test a REST endpoint
  - Validate responses and status codes
  - Write SQL queries to verify data

Round 4 · Manager / behavioural (30–45 min)
  - "Tell me about a bug you caught"
  - "How do you prioritise testing?"
  - Project walkthrough, teamwork, communication

Round 5 · HR / offer (20–30 min)
  - Compensation, joining, notice
  - Sometimes a final culture-fit call

What we coach for
  ✓ Clear explanations, not memorised answers
  ✓ Structured thinking (inputs → process → checks)
  ✓ Honest "I don't know, but here's how I'd find out"