How Automation Testing Works

Before writing any automation code, you need a mental model of what happens when a test runs. Understanding this end-to-end flow makes every concept in this path click into place.

The Flow: From Code to Result

Every automated test follows the same pattern: Arrange → Act → Assert.

1. Arrange — Set up the preconditions. Open the browser, navigate to the page, prepare test data.
2. Act — Perform the action. Click a button, fill a form, call an API.
3. Assert — Verify the result. Check the page title, verify a success message, confirm a database record.

@Test
public void testAddToCart() {
    // Arrange
    WebDriver driver = new ChromeDriver();
    driver.get("https://shop.example.com/products/laptop");

    // Act
    driver.findElement(By.id("add-to-cart")).click();

    // Assert
    String cartCount = driver.findElement(By.id("cart-count")).getText();
    Assert.assertEquals(cartCount, "1");

    driver.quit();
}

What Happens Under the Hood

When you run a Selenium test, several components work together:

Your Java Code
      ↓ (Selenium API call)
Selenium WebDriver Library
      ↓ (HTTP request)
Browser Driver (chromedriver)
      ↓ (DevTools Protocol)
Chrome Browser
      ↓ (renders page, clicks element)
Result sent back up the chain
      ↓
TestNG compares actual vs expected
      ↓
✅ PASS  or  ❌ FAIL

You do not need to understand every layer right now. The key takeaway: your Java code talks to the Selenium library, which talks to the browser driver, which controls the browser. When you write driver.findElement(By.id("login")).click(), that single line triggers this entire chain.

The Testing Pyramid

Not all tests need a browser. The testing pyramid defines how many tests to have at each level:

Most of your tests should be unit tests (fast, reliable). API tests sit in the middle. UI tests at the top are the slowest and most fragile — a single CSS change can break them. This path focuses on UI automation with Selenium, but understanding the pyramid helps you make better decisions about what to test and how.

Types of Automated Tests

Try It Yourself

Exercise 1: Read the LoginTest code example at the top of this lesson. Identify the Arrange, Act, and Assert sections in it.

Exercise 2: For each scenario, identify the test type (smoke, regression, functional, performance): (a) Running 200 tests before a release to check nothing broke (b) Checking if login works right after deploying to production (c) Verifying that the search feature returns correct results (d) Testing whether the app crashes under 1000 simultaneous users.