Why reports communicate test results in Selenium Java - Automation Benefits in Action

Verify test report shows correct test results after login test

Preconditions (2)

Step 1: Open the login page

Step 2: Enter '[e-mail]' in the email field

Step 3: Enter 'Pass123!' in the password field

Step 4: Click the Login button

Step 5: Verify the dashboard page is displayed

Step 6: Generate the test report after test execution

✅ Expected Result: The test report should show the login test as passed with details of steps executed

Automation Requirements - Selenium with TestNG

Assertions Needed:

Verify dashboard page URL after login

Verify test report contains the login test result as passed

Best Practices:

Use explicit waits to wait for dashboard page

Use Page Object Model for page interactions

Generate and save test report automatically after test run

Automated Solution

Selenium Java

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
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.AfterClass;
import org.testng.annotations.BeforeClass;
import org.testng.annotations.Test;
import java.time.Duration;

public class LoginTest {
    private WebDriver driver;
    private WebDriverWait wait;

    @BeforeClass
    public void setUp() {
        System.setProperty("webdriver.chrome.driver", "./chromedriver");
        driver = new ChromeDriver();
        wait = new WebDriverWait(driver, Duration.ofSeconds(10));
    }

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

        WebElement emailField = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("email")));
        emailField.sendKeys("[e-mail]");

        WebElement passwordField = driver.findElement(By.id("password"));
        passwordField.sendKeys("Pass123!");

        WebElement loginButton = driver.findElement(By.id("loginBtn"));
        loginButton.click();

        // Wait for dashboard page URL
        wait.until(ExpectedConditions.urlContains("/dashboard"));

        String currentUrl = driver.getCurrentUrl();
        Assert.assertTrue(currentUrl.contains("/dashboard"), "Dashboard page should be displayed after login");
    }

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

This test script uses Selenium WebDriver with TestNG framework to automate the login test.

setUp() initializes the ChromeDriver and explicit wait.

testValidLogin() opens the login page, enters the given email and password, clicks login, and waits until the dashboard page URL appears. Then it asserts the URL contains '/dashboard' to confirm successful login.

tearDown() closes the browser after the test.

TestNG automatically generates a test report after execution showing if the test passed or failed. This report communicates the test result clearly to stakeholders.

Common Mistakes - 3 Pitfalls

Using Thread.sleep() instead of explicit waits

Hardcoding XPath selectors that are brittle

Not closing the browser after test

Bonus Challenge

Now add data-driven testing with 3 different sets of login credentials (valid and invalid) to verify login behavior.

Show Hint

Practice

1. Why are test reports important in software testing?

easy

A. They show if tests passed or failed clearly

B. They write the test code automatically

C. They replace the need for manual testing

D. They increase the speed of the software

Solution

1. Step 1: Understand the purpose of test reports

   Test reports summarize the results of tests, showing which tests passed or failed.

2. Step 2: Compare options with the purpose

   Only They show if tests passed or failed clearly correctly states that reports show test results clearly. Other options describe unrelated functions.

3. Final Answer:

   They show if tests passed or failed clearly -> Option A

4. Quick Check:

   Test reports communicate results = B [OK]

Hint: Remember: reports tell if tests passed or failed [OK]

Common Mistakes:

• Thinking reports write test code
• Believing reports replace manual testing
• Confusing reports with software speed tools

2. Which of the following is the correct way to generate a test report in Selenium with Java?

easy

A. Using Thread.sleep() to delay report generation

B. Manually writing test results to a text file inside each test

C. Using TestNG listeners to create reports automatically

D. Calling System.out.println() to print results only

Solution

1. Step 1: Identify standard report generation methods in Selenium Java

   TestNG listeners are commonly used to generate reports automatically after tests run.

2. Step 2: Evaluate other options

   Manually writing files or printing results is not standard or efficient. Using sleep delays tests but does not generate reports.

3. Final Answer:

   Using TestNG listeners to create reports automatically -> Option C

4. Quick Check:

   Automatic report generation = D [OK]

Hint: Use TestNG listeners for automatic reports [OK]

Common Mistakes:

• Thinking print statements create reports
• Using sleep to control report timing
• Writing manual files instead of using tools

3. Given the following TestNG test output snippet:

Tests run: 5, Failures: 1, Skips: 0

What does this report tell you?

medium

A. One test failed and no tests were skipped

B. All tests passed successfully

C. No tests were run

D. One test was skipped and all others passed

Solution

1. Step 1: Interpret the test report numbers

   Tests run: 5 means 5 tests executed; Failures: 1 means 1 test failed; Skips: 0 means no tests were skipped.

2. Step 2: Match interpretation to options

   Only One test failed and no tests were skipped correctly states one test failed and none skipped. Others are incorrect based on the numbers.

3. Final Answer:

   One test failed and no tests were skipped -> Option A

4. Quick Check:

   Failures=1, Skips=0 = A [OK]

Hint: Failures count shows how many tests failed [OK]

Common Mistakes:

• Assuming zero failures means no tests run
• Confusing skipped tests with failed tests
• Ignoring the failures count

4. You see a test report showing all tests passed, but your application still has bugs. What is the most likely reason?

medium

A. The test framework is broken and shows wrong results

B. The report is generated before tests run

C. The application is updated after tests finish

D. The tests do not cover all important features

Solution

1. Step 1: Analyze why tests pass but bugs remain

   If tests pass but bugs exist, it usually means tests do not cover all features or scenarios.

2. Step 2: Evaluate other options

   Reports generated before tests or broken frameworks are rare and obvious errors. Application updates after tests do not explain bugs in tested features.

3. Final Answer:

   The tests do not cover all important features -> Option D

4. Quick Check:

   Incomplete test coverage = C [OK]

Hint: Passing tests don't guarantee full coverage [OK]

Common Mistakes:

• Blaming report timing without evidence
• Assuming framework is always broken
• Ignoring test coverage gaps

5. How can automated test reports improve team communication about software quality?

hard

A. By replacing all manual testing with automated tests

B. By providing clear, quick feedback on test results to all team members

C. By hiding failed tests to avoid confusion

D. By delaying test results until the end of the project

Solution

1. Step 1: Understand the role of automated test reports in communication

   Automated reports give fast, clear feedback on test results, helping teams know software quality status quickly.

2. Step 2: Evaluate options for communication improvement

   Only By providing clear, quick feedback on test results to all team members describes how reports improve communication. Other options describe incorrect or harmful practices.

3. Final Answer:

   By providing clear, quick feedback on test results to all team members -> Option B

4. Quick Check:

   Clear, fast feedback improves communication = A [OK]

Hint: Reports give fast, clear feedback to teams [OK]

Common Mistakes:

• Thinking reports replace manual testing
• Believing hiding failures helps communication
• Assuming delays improve understanding