TestNG default reports in Selenium Java

Introduction

TestNG default reports help you see which tests passed or failed without extra setup. They give quick feedback on your test results.

After running automated tests to check if all tests passed.

When you want a simple summary of test results without custom reports.

To quickly find failed tests and their error messages.

When sharing test results with your team in a standard format.

To track test execution over time using the generated report files.

Syntax

Selenium Java

TestNG automatically generates reports after test execution.

Reports are saved in the 'test-output' folder by default.

You do not need to write code to create these reports.

The main report files are index.html and emailable-report.html.

Reports include test status, execution time, and error details for failures.

Examples

A simple test that will pass and appear in the default report.

Selenium Java

@Test
public void testExample() {
    Assert.assertTrue(true);
}

A test that fails and will be marked as failed in the default report.

Selenium Java

@Test
public void testFail() {
    Assert.assertTrue(false);
}

Sample Program

This test class has two tests: one passes and one fails. After running with TestNG, the default report will show one pass and one fail.

Selenium Java

import org.testng.Assert;
import org.testng.annotations.Test;

public class SampleTest {

    @Test
    public void testPass() {
        Assert.assertTrue(true);
    }

    @Test
    public void testFail() {
        Assert.assertTrue(false, "This test is designed to fail.");
    }
}

Important Notes

TestNG creates the test-output folder automatically after tests run.

You can open test-output/index.html in a browser to see a detailed report.

Reports update every time you run tests, showing the latest results.

Summary

TestNG default reports show test results automatically after running tests.

They help quickly identify passed and failed tests with error details.

No extra code is needed to generate these reports; just run your tests.

Practice

1. What is the main purpose of TestNG default reports?

easy

A. To write custom test cases manually

B. To automatically show test results after running tests

C. To compile Java code before testing

D. To create database backups

Solution

1. Step 1: Understand what TestNG default reports do

   TestNG default reports automatically display the results of tests after execution without extra coding.

2. Step 2: Compare options with this function

   Only To automatically show test results after running tests matches this description; others describe unrelated tasks.

3. Final Answer:

   To automatically show test results after running tests -> Option B

4. Quick Check:

   TestNG default reports = automatic test result display [OK]

Hint: Default reports show results automatically after tests run [OK]

Common Mistakes:

• Thinking reports require extra code
• Confusing reports with code compilation
• Assuming reports manage databases

2. Which file is generated by TestNG by default to show test results?

easy

A. test-output/index.html

B. src/test/java/Test.java

C. pom.xml

D. log.txt

Solution

1. Step 1: Identify the default report file location

   TestNG generates reports inside the 'test-output' folder, with 'index.html' as the main report file.

2. Step 2: Check other options for correctness

   Other files are unrelated: source code, build config, or logs.

3. Final Answer:

   test-output/index.html -> Option A

4. Quick Check:

   Default report file = test-output/index.html [OK]

Hint: Look inside test-output folder for default reports [OK]

Common Mistakes:

• Confusing source code files with report files
• Expecting reports in pom.xml or logs
• Not checking the test-output directory

3. Given this TestNG test run, what will the default report show if one test fails and two pass?

medium

A. Passed: 2, Failed: 1, Skipped: 0

B. Passed: 3, Failed: 0, Skipped: 0

C. Passed: 1, Failed: 2, Skipped: 0

D. Passed: 0, Failed: 3, Skipped: 0

Solution

1. Step 1: Analyze the test results given

   There are two tests that passed and one test that failed.

2. Step 2: Match the counts to the report format

   The report shows counts as Passed: 2, Failed: 1, Skipped: 0.

3. Final Answer:

   Passed: 2, Failed: 1, Skipped: 0 -> Option A

4. Quick Check:

   Test counts in report = Passed 2, Failed 1 [OK]

Hint: Count tests passed and failed to match report summary [OK]

Common Mistakes:

• Mixing passed and failed counts
• Assuming skipped tests when none exist
• Misreading the test result numbers

4. You ran TestNG tests but the default report shows no tests executed. What is the likely cause?

medium

A. Java version is outdated

B. TestNG jar file is corrupted

C. Report folder is manually deleted

D. Test methods are missing the @Test annotation

Solution

1. Step 1: Understand why no tests run

   If test methods lack the @Test annotation, TestNG will not recognize or run them.

2. Step 2: Evaluate other options

   Corrupted jar or Java version issues usually cause errors, not silent no tests. Deleting report folder does not affect test execution.

3. Final Answer:

   Test methods are missing the @Test annotation -> Option D

4. Quick Check:

   No @Test annotation = no tests run [OK]

Hint: Check @Test annotation on test methods first [OK]

Common Mistakes:

• Assuming report folder deletion stops tests
• Blaming Java version without error messages
• Ignoring missing @Test annotations

5. How can you customize the TestNG default report to include screenshots on failure?

hard

A. By disabling default reports and writing logs to console only

B. By editing the test-output/index.html file manually after tests run

C. By adding listeners and embedding screenshots in the report via ITestListener

D. By renaming the test-output folder before running tests

Solution

1. Step 1: Understand default report customization

   TestNG default reports do not support screenshots by default; customization requires listeners like ITestListener.

2. Step 2: Evaluate options for adding screenshots

   Adding listeners to capture screenshots on failure and embed them is the correct approach. Manual editing or renaming folders won't add screenshots. Disabling reports removes them entirely.

3. Final Answer:

   By adding listeners and embedding screenshots in the report via ITestListener -> Option C

4. Quick Check:

   Use ITestListener to add screenshots [OK]

Hint: Use ITestListener to add screenshots on failure [OK]

Common Mistakes:

• Trying to edit report files manually
• Renaming folders expecting new features
• Disabling reports instead of customizing