{"id":37065,"date":"2016-06-29T16:10:13","date_gmt":"2016-06-29T10:40:13","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=37065"},"modified":"2017-05-25T10:50:51","modified_gmt":"2017-05-25T05:20:51","slug":"how-to-use-extentreport-in-a-framework-2","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/how-to-use-extentreport-in-a-framework-2\/","title":{"rendered":"How to use ExtentReport in a framework"},"content":{"rendered":"

The other day while I was executing my TestNG test cases in the Selenium WebDriver, all my test cases got executed, and the report also showed correctly. However, I usually don’t find its user interface very friendly especially when it’s about creating reports. That’s when I came across a user friendly reporting tool called\u00a0ExtentReport<\/strong>.<\/p>\n

ExtentReport is an HTML reporting library for Java, which can be used with Selenium WebDriver. We can use this tool within our TestNG automation framework. As an automation tester<\/a>, it\u2019s expected of you to provide detailed yet reports and present it to the administration group. ExtentReport is a simple to use tool to make excellent execution reports.<\/p>\n

Process to Set up ExtentReport:<\/strong><\/p>\n

    \n
  1. Install and set up Java on your system.<\/li>\n
  2. Now setup Eclipse.<\/li>\n
  3. Launch Eclipse and create a Maven project.<\/li>\n
  4. Add Selenium, TestNG, ExtentReport dependency in the pom.xml file.<\/li>\n<\/ol>\n

    ExtentReport dependency in our maven project, use the below snippet:-<\/p>\n

    \"five\"<\/p>\n

    Use Case in which we are going to mechanize<\/strong><\/p>\n

      \n
    1. Check the current URL of the web page<\/li>\n
    2. Enter invalid email id in the Sign Up content box<\/li>\n
    3. Click on the Sign Up button<\/li>\n
    4. To verify the error message.<\/li>\n<\/ol>\n

      Create a Simple TestNG Script<\/strong>
      \nFollowing is the code snippet for our use case.<\/p>\n

      \"one\"<\/strong><\/p>\n

        \n
      1. startTest(\u201cTestCaseName\u201d, \u201cDescription\u201d) : <\/strong>It starts the current test.<\/li>\n<\/ol>\n

        \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 TestCaseName \u2013<\/strong> It will print the name of the Test Case in the Report.
        \n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Description \u2013 <\/strong>It will print the description of the Test case.<\/p>\n

          \n
        1. assignAuthor(\u201cAuthorName\u201d) : <\/strong>Test case designer name is mentioned here.<\/li>\n
        2. assignCategory(\u201cCategoryName\u201d) : <\/strong>Category of the Test Case displays here.<\/li>\n
        3. log(LogStatus.PASS, \u201cStep details\u201d): <\/strong>It’s a repository which keeps the information about the test cases whether passed or failed.<\/li>\n
        4. endTest(test) : <\/strong>Current test case ends here.<\/li>\n
        5. flush() :<\/strong> Once the session is finished, specifically call the flush method.<\/li>\n
        6. close() : <\/strong>Call this method at the very end in the @AfterSuite annotation, it ought to be called just once.<\/li>\n<\/ol>\n

          Following is the ‘extent-config.xml’ snippet.<\/p>\n

          \"extent-config\"<\/p>\n

          Once the test cases are run successfully, the report will be created under your folder. Now, go to the folder and view the .html report.
          \nFor e.g.:<\/strong> The path of the report will be D:\\MyExtentReport.html<\/strong><\/p>\n

          ExtentReport Architecture<\/strong>
          \nAfter executing the test cases, the ExtentReport<\/strong> design will look like this.<\/p>\n

          \u00a0\"two\" <\/strong><\/p>\n

          \"three\"\u00a0\"four\"<\/p>\n

          In this report, the main page is the dashboard where:-<\/p>\n

            \n
          • You can view the total number of test cases and test steps<\/li>\n
          • Start time and End time are displayed<\/li>\n
          • Number of test cases passed, failed, skipped, and so on information is provided<\/li>\n
          • Number of steps of test cases passed, failed, and so on data is given<\/li>\n
          • Pass Percentage of total number of test cases is given<\/li>\n
          • Category Name of the test cases is likewise shown on the dashboard.<\/li>\n<\/ul>\n

            Clicking on the middle tab, I will be able to see the suite level information and its status (whether it\u2019s pass or fail). On clicking the respective test case name, it will show the test case details: its start time, end time and execution time.<\/p>\n

            Points of interest of ExtentReport<\/strong><\/p>\n

              \n
            1. Open source reporting library.<\/li>\n
            2. Provide delightful and responsive UI.<\/li>\n
            3. Gives dashboard to the whole run.<\/li>\n
            4. Exceptionally easy to utilize API.<\/li>\n
            5. Effortlessly coordinate test-runner logs.<\/li>\n
            6. Parallel execution of classes and strategies upheld.<\/li>\n
            7. It can also be configured on Jenkins server.<\/li>\n<\/ol>\n

              It’s a useful storehouse having an extraordinary HTML reporting feature. Automation Testers ought to utilize this report because of its effective reporting by which anybody can understand easily which test case is working appropriately and which falls flat.<\/p>\n

              HAPPY TESTING!<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

              The other day while I was executing my TestNG test cases in the Selenium WebDriver, all my test cases got executed, and the report also showed correctly. However, I usually don’t find its user interface very friendly especially when it’s about creating reports. That’s when I came across a user friendly reporting tool called\u00a0ExtentReport. ExtentReport […]<\/p>\n","protected":false},"author":107,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":303},"categories":[1818,1816],"tags":[1561,14,4844,1562],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/37065"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/107"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=37065"}],"version-history":[{"count":1,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/37065\/revisions"}],"predecessor-version":[{"id":52465,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/37065\/revisions\/52465"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=37065"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=37065"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=37065"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}