How Uncodemy Trains Students for QA Tester Roles

# Sample test case — login form
# This is the format Uncodemy students learn to write in Phase 1.

Test Case ID:      TC_LOGIN_001
Title:             Login with valid credentials
Priority:          High
Severity:          Critical
Preconditions:     User exists with email priya@example.com
                   Password: Test@1234
                   Browser: Chrome, Firefox, Edge

Steps:
  1. Navigate to https://app.example.com/login
  2. Enter "priya@example.com" in Email field
  3. Enter "Test@1234" in Password field
  4. Click "Sign In" button

Expected Result:
  - User is redirected to /dashboard
  - Header shows "Welcome, Priya"
  - Session cookie is set (expires in 24 hours)

Actual Result:
  - [Fill in after execution]

Status:            Pass / Fail
Tested By:         [Name]
Date:              [Date]

---

Test Case ID:      TC_LOGIN_002
Title:             Login with invalid password
Expected Result:   Inline error: "Incorrect email or password."
                   User remains on /login page.
                   Failed attempt is logged.

---

Test Case ID:      TC_LOGIN_003
Title:             Login with empty fields
Expected Result:   Client-side validation blocks submission.
                   Email field shows: "Email is required."
                   Password field shows: "Password is required."

# What this teaches:
# - Test cases are specific enough that anyone can execute them
# - Every test has a clear expected result
# - Every test is traceable to a requirement
# Interviewers often ask you to write one on the spot.

# Sample defect report
# The most-used document in a QA tester's first job.

Defect ID:         BUG-2026-0142
Title:             Discount field accepts negative values
Reporter:          Meera K.
Reported On:       2026-09-12
Environment:       Chrome 120, Windows 11, Staging build 4.2.7

Severity:          High
Priority:          P1

Steps to Reproduce:
  1. Log in as a customer
  2. Add any product to the cart
  3. Proceed to checkout
  4. In the "Discount code" field, enter "-500"
  5. Click "Apply"

Actual Result:
  - Discount is applied as -₹500
  - Order total increases by ₹500
  - No validation error is shown

Expected Result:
  - Discount code field rejects negative values
  - Error message: "Invalid discount code"
  - Order total remains unchanged

Attachments:
  - screenshot_checkout_negative_discount.png
  - console_log.txt

Additional Notes:
  - Reproduces on Chrome 120 and Firefox 121
  - Does not reproduce on mobile Safari
  - Likely a missing validation in the discount service

---

# Why a good defect report matters:
# - Developers need steps, not descriptions
# - Severity and priority drive the fix order
# - Screenshots and logs speed up debugging
# - Poor reports get ignored; good ones get fixed

# Uncodemy students practice writing 20+ defect reports
# on live projects during Phase 1.

// Selenium — login page test
// What automation looks like in Phase 2.

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.support.ui.ExpectedConditions;
import org.openqa.selenium.support.ui.WebDriverWait;
import org.testng.Assert;
import org.testng.annotations.AfterMethod;
import org.testng.annotations.BeforeMethod;
import org.testng.annotations.Test;

import java.time.Duration;

public class LoginTest {

    private WebDriver driver;
    private WebDriverWait wait;

    @BeforeMethod
    public void setUp() {
        driver = new ChromeDriver();
        driver.manage().window().maximize();
        wait = new WebDriverWait(driver, Duration.ofSeconds(10));
    }

    @Test
    public void testLoginWithValidCredentials() {
        driver.get("https://app.example.com/login");

        driver.findElement(By.id("email")).sendKeys("priya@example.com");
        driver.findElement(By.id("password")).sendKeys("Test@1234");
        driver.findElement(By.cssSelector("button[type='submit']")).click();

        // Wait for dashboard to load
        wait.until(ExpectedConditions.urlContains("/dashboard"));

        String welcome = driver.findElement(By.cssSelector(".welcome-banner")).getText();
        Assert.assertTrue(welcome.contains("Welcome, Priya"),
            "Welcome banner should show the user's name");
    }

    @Test
    public void testLoginWithInvalidPassword() {
        driver.get("https://app.example.com/login");

        driver.findElement(By.id("email")).sendKeys("priya@example.com");
        driver.findElement(By.id("password")).sendKeys("wrongPassword");
        driver.findElement(By.cssSelector("button[type='submit']")).click();

        // Error should appear
        String error = wait.until(
            ExpectedConditions.visibilityOfElementLocated(
                By.className("error-message"))
        ).getText();

        Assert.assertEquals(error, "Incorrect email or password.");
        Assert.assertTrue(driver.getCurrentUrl().contains("/login"));
    }

    @AfterMethod
    public void tearDown() {
        if (driver != null) driver.quit();
    }
}

// What this teaches:
// - Page object pattern (students refactor to this in Phase 2)
// - Explicit waits over Thread.sleep
// - Assertions with clear failure messages
// - Test independence (each @Test sets up its own state)
// - Proper cleanup in @AfterMethod

// This is the kind of test suite that gets a QA candidate hired.