Registry Synced

๐Ÿค– Test Automation

224 words
1 min read

Reading compass

Now ยท 1. ๐ŸŽฏ Learning Objectives

๐Ÿค– Test Automation

1. ๐ŸŽฏ Learning Objectives

  • Explain Selenium WebDriver architecture
  • Describe CI/CD pipeline integration for tests
  • Trace the bug lifecycle: New โ†’ Assigned โ†’ Fixed โ†’ Verified โ†’ Closed

2. ๐Ÿ“– Core Content

3.1 Selenium WebDriver

Selenium automates browser interactions:
  • Find elements: By ID, class, XPath, CSS selector
  • Interact: Click, type, select
  • Assert: Verify expected behavior

3.2 Page Object Model

Encapsulate page elements and actions in reusable classes:
java
public class LoginPage {
    private WebDriver driver;
    private By usernameField = By.id("username");
    private By passwordField = By.id("password");
    private By loginButton = By.id("login");
    public void login(String user, String pass) {
        driver.findElement(usernameField).sendKeys(user);
        driver.findElement(passwordField).sendKeys(pass);
        driver.findElement(loginButton).click();
    }
}

3.3 CI/CD Integration

Tests run automatically on every commit. Pipeline stages:
  1. Build
  2. Unit tests
  3. Integration tests
  4. UI tests (Selenium)
  5. Deploy

3.4 Bug Lifecycle

New โ†’ Assigned โ†’ Fixed โ†’ Verified โ†’ Closed Severity vs Priority: Severity = impact on system. Priority = urgency to fix.

4. ๐Ÿ“ Practice Questions

Q1: What is the purpose of the Page Object Model in Selenium?
Answer: POM encapsulates page elements and actions into reusable classes. Benefits: reduces code duplication, improves maintainability (one place to update when UI changes), and makes tests more readable. Join Discord PreviousTDD & Mutation TestingNextIntegration & Regression
Document outline

Keep your place and jump directly to a heading.

Table of contents

No note selected

Open a chapter to see its outline, backlinks, and sources here.