TestNG Report

TESTNG REPORTING:

 

A perfect test automation tool is what you need for the successful execution of the testing requirements in the Agile process. And there are multiple factors which play a critical role in the formation of a robust automation framework.

One such factor is reporting which not only make you aware of the status of the success or failure but helps you in finding out the potential bugs. So, you should mindfully choose how you are going to generate reports in Selenium WebDriver project. That’s where this post would lead you to make a decision.

TestNG Reporting:

TestNG library brings a very convenient reporting feature. Once you execute the tests, TestNG generates a test output folder at the root of the project. It combines two kinds of reports.

1.Detailed Report.

You can find this report in the <index.html> file. It combines the detailed information like the errors, test groups, execution time, step-by-step logs and TestNG XML file.

2.Summary Report.

It is the trimmed version and informs about the test pass/fail/skip count. You can see it from the <emailable-report.html> file. It’s an email friendly report which you can embed and share with the stakeholders.

Q1-Importance of Reporting in Selenium?

1- Reports help you to identify the status of the test case (Pass/Fail/Skip).

2- Using reports we calculate time taken by each test case that helps to calculate ROI (Return on Investment).

3- You can share automation reports with your team and clients as well to share the status of testing progress etc.

Q2- Does selenium support report generation?

Ans- No Selenium will only help you to automate your web application. If you want to generate reports then we can use Third party tools that we can integrate and can generate reports.

Here TestNG comes into the picture.

Q3- Do we need to write some script or any additional code for reports?
Ans- No we do not have to write any additional code for report generation (if using TestNG). We need to refresh our project and we will get 1 additional folder (default suite) inside that folder we will get all the reports.

Q4- What are the essential qualities of a good test report?

  • Brevity –
    • A report should be short and concise.
    • It should clearly state the proportion of total no. of success or failure.
  • Trackability –
    • Captures all the footprints that could lead to the root cause of a failure.
  • Traceability –
    • It must provide the ability to review the following.
      • Historical data for test cases and failures.
      • Age of a particular failure.
    • Sharable –
      • It should support a format which you can share through email or integrate with CI tools like Jenkins/Bamboo.
    • Test coverage –
      • It should highlight the test coverage for the following.
        • Test coverage of the module under test.
        • Test coverage of the application under test.

Leave a Reply

Your email address will not be published. Required fields are marked *