Capture Screenshot in Extent Reports will discuss about capturing the screenshot of a particular failure step in the HTML report.  In our previous blog we have seen how to log the messages in the report. Same way here we will capture the screenshot for a particular failure step. The screenshot will give the information about on which screen the script  got failed during the execution. Then we can easily identify the issue by looking into the report.

For this we need to use the Log() method of ExtentTest class. To log the screenshot in the report we need to pass the path of the screenshot to the log method as a parameter. So, before logging the screenshot to the report we need to capture the screenshot of that particular failure method and place it in a folder from there we need to get the path of the screenshot file and pass it to the log method.

Below is the sample program to capture screenshot in the report:

using NUnit.Framework;
using NUnit.Framework.Interfaces;
using OpenQA.Selenium;
using OpenQA.Selenium.Firefox;
using RelevantCodes.ExtentReports;
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace ExtentReportsDemo
{
    [TestFixture]
    public class CapturingScreenshot
    {
        ExtentReports extent;
        ExtentTest test;
        IWebDriver driver;

        [OneTimeSetUp]
        public void Init()
        {
            string path = System.Reflection.Assembly.GetCallingAssembly().CodeBase;
            string actualPath = path.Substring(0, path.LastIndexOf("bin"));
            string projectPath = new Uri(actualPath).LocalPath;
            string reportPath = projectPath + "Reports\\ExtentScreenshot.html";
            extent = new ExtentReports(reportPath, true);
        }

        [Test]
        public void CaptureScreenshot()
        {
            test = extent.StartTest("CaptureScreenshot");
            driver = new FirefoxDriver();
            driver.Navigate().GoToUrl("https://automationtesting.in");
            string title = driver.Title;
            Assert.AreEqual("Home - Automation Test", title);
            test.Log(LogStatus.Pass, "Test Passed");
        }

        [TearDown]
        public void GetResult()
        {
            var status = TestContext.CurrentContext.Result.Outcome.Status;
            var stackTrace = "<pre>" + TestContext.CurrentContext.Result.StackTrace + "</pre>";
            var errorMessage = TestContext.CurrentContext.Result.Message;

            if (status == TestStatus.Failed)
            {
                string screenShotPath = GetScreenShot.Capture(driver, "ScreenShotName");
                test.Log(LogStatus.Fail, stackTrace + errorMessage);
                test.Log(LogStatus.Fail, "Snapshot below: " + test.AddScreenCapture(screenShotPath));
            }
            extent.EndTest(test);
        }

        [OneTimeTearDown]
        public void Endreport()
        {
            driver.Close();
            extent.Flush();
            extent.Close();
        }
    }
}

In the above program we have written  test.Log method to log the screenshot into the extent reports. This information will logged in the report with time stamp.




Below is the program to capture the screenshot and it will place the screenshot in a particular folder and will return the path of the screenshot. Will use that path to capture the screenshot in the HTML report for a failure step.

using OpenQA.Selenium;
using System;
using System.Collections.Generic;
using System.Drawing.Imaging;
using System.IO;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace ExtentReportsDemo
{
    public class GetScreenShot
    {
        public static string Capture(IWebDriver driver, string screenShotName)
        {
            ITakesScreenshot ts = (ITakesScreenshot)driver;
            Screenshot screenshot = ts.GetScreenshot();
            string pth = System.Reflection.Assembly.GetCallingAssembly().CodeBase;
            string finalpth = pth.Substring(0, pth.LastIndexOf("bin")) + "ErrorScreenshots\\" + screenShotName + ".png";
            string localpath = new Uri(finalpth).LocalPath;
            screenshot.SaveAsFile(localpath, ImageFormat.Png);
            return localpath;
        }
    }
}

Above program will return the path of the screenshot.

Below is the output of the above program:

Please watch the YouTube video of this blog for better understanding.

The post Capture Screenshot in Extent Reports – CSharp appeared first on Selenium Webdriver Appium Complete Tutorial.

Extent Reports Log Generation will discuss about how to generate log steps in the Extent Reports. While running the test suite user want to log some information about the execution in the report. This information will help the user to understand the test step execution flow and any failures during the test suite execution.

By using Extent Reports we can generate logs in the HTML report. For this we need use the Log() method of the ExtentTest Class. By using this method not only log the step information, we can provide the Pass, Fail and Skip information of the particular test case. To log the information we need to use the LogStatus.Info as first parameter in the Log() method. And we need to use LogStatus.Pass for the passed test case and LogStatus.Fail for the failed test cases.

Below is the sample program for generating step logs in the report:

using NUnit.Framework;
using RelevantCodes.ExtentReports;
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace ExtentReportsDemo
{
    [TestFixture]
    public class CreatingStepLogs
    {
        public ExtentReports extent;
        public ExtentTest test;

        [OneTimeSetUp]
        public void StartReport()
        {
            string path = System.Reflection.Assembly.GetCallingAssembly().CodeBase;
            string actualPath = path.Substring(0, path.LastIndexOf("bin"));
            string projectPath = new Uri(actualPath).LocalPath;
            string reportPath = projectPath + "Reports\\ExtentStepLogs.html";
            extent = new ExtentReports(reportPath, true);
        }

        [Test]
        public void StepLogsGeneration()
        {
            test = extent.StartTest("StepLogsGeneration");
            test.Log(LogStatus.Info, "StartTest() method will return the Extent Test object ");
            test.Log(LogStatus.Info, "I am in actual test method");
            test.Log(LogStatus.Info, "We Can Write The Actual Test Logic In This Test");
        }

        [OneTimeTearDown]
        public void TearDown()
        {
            extent.EndTest(test);
            test.Log(LogStatus.Info, "EndTest() method will stop capturing information about the test log");
            extent.Flush();
            test.Log(LogStatus.Info, "Flush() method of ExtentReports wil push/write everything to the document");
            test.Log(LogStatus.Info, "Close() method will clear/close all resource of the ExtentReports object");
            extent.Close();
        }
    }
}

In the above program we have written so many test.Log methods to log the information into the extent reports. This information will logged in the report with time stamp.




Below is the output/report of the above program:

Please watch the YouTube video of this blog for better understanding.

The post Extent Reports Log Generation – CSharp appeared first on Selenium Webdriver Appium Complete Tutorial.

Extent reports are very rich HTML reports for the selenium webdriver. This report will give so much of information about the execution status. The extra information can be provided from the external XML file. Once you create the XML file need to load in the program to read the configuration.

We can provide below information to the report using XML file:

1. Report Title
2. Report Name
3. Report Headline
4. Date Format
5. Time Format

Apart from the above we can provide HostName, Environment Information and User Name etc… from the program.

Below is the sample program:

using NUnit.Framework;
using NUnit.Framework.Interfaces;
using RelevantCodes.ExtentReports;
using System;
using System.Collections.Generic;
using System.IO;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace ExtentReportsDemo
{
    [TestFixture]
    public class BasicReport
    {
        public ExtentReports extent;
        public ExtentTest test;

        [OneTimeSetUp]
        public void StartReport()
        {
            string path = System.Reflection.Assembly.GetCallingAssembly().CodeBase;
            string actualPath = path.Substring(0, path.LastIndexOf("bin"));
            string projectPath = new Uri(actualPath).LocalPath;
            string reportPath = projectPath + "Reports\\MyOwnReport.html";

            extent = new ExtentReports(reportPath, true);
            extent
            .AddSystemInfo("Host Name", "Krishna")
            .AddSystemInfo("Environment", "QA")
            .AddSystemInfo("User Name", "Krishna Sakinala");
            extent.LoadConfig(projectPath + "extent-config.xml");
        }
        
        [Test]
        public void DemoReportPass()
        {
            test = extent.StartTest("DemoReportPass");
            Assert.IsTrue(true);
            test.Log(LogStatus.Pass, "Assert Pass as condition is True");
        }

        [Test]
        public void DemoReportFail()
        {
            test = extent.StartTest("DemoReportFail");
            Assert.IsTrue(false);
            test.Log(LogStatus.Pass, "Assert Fail as condition is False");
        }

        [TearDown]
        public void GetResult()
        {
            var status = TestContext.CurrentContext.Result.Outcome.Status;
            var stackTrace = "<pre>" + TestContext.CurrentContext.Result.StackTrace + "</pre>";
            var errorMessage = TestContext.CurrentContext.Result.Message;

            if (status == TestStatus.Failed)
            {
                test.Log(LogStatus.Fail, stackTrace + errorMessage);
            }
            extent.EndTest(test);
        }

        [OneTimeTearDown]
        public void EndReport()
        {
            extent.Flush();
            extent.Close();
        }
    }
}

In the above program, we have used two classes called ExtentReports, ExtentTest. These two classes objects will help us to create a rich HTML reports with lot of useful information. ExtentReports  will take the HTML report file path as an argument and it will create the report file with the mentioned name in the mentioned location. And ExtentTest will be used to log the so much information to the report like PASS, FAIL  and SKIP status of the executed tests.

Important points to be remember:

1. ExtentReports will create the report file.
2. ExtentTest will log the information in the report.
3. StartTest() method of ExtentReports class is the starting point of the test and it will return the ExtentTest object.
4. We need to capture that object into ExtentTest object.
5. Used this reference to log the information into the report.
6. ExtentReports object will be used to add the report information like Title, Header and Theme etc..
7. And the above configuration need to passed from the external XML file using LoadConfig() method of ExtentReports class. It will take the XML file path as argument.
8. EndTest() method of ExtentReports will stop capturing information about the test log.
9. Flush() method of ExtentReports will push/write everything to the document.
10. Close() method of ExtentReports will clear/close all resource of the ExtentReports object.

Below is the sample configuration file:

<?xml version="1.0" encoding="UTF-8"?>
<extentreports>
  <configuration>
    <!-- report theme -->
    <!-- standard, dark -->
    <theme>standard</theme>
 
    <!-- document encoding -->
    <!-- defaults to UTF-8 -->
    <encoding>UTF-8</encoding>
    
    <!-- protocol for script and stylesheets -->
    <!-- defaults to https -->
    <protocol>https</protocol>
    
    <!-- title of the document -->
    <documentTitle>AutomationTesting.in</documentTitle>
    
    <!-- report name - displayed at top-nav -->
    <reportName>Automation Testing Report</reportName>
    
    <!-- report headline - displayed at top-nav, after reportHeadline -->
    <reportHeadline>- QA Environment</reportHeadline>
    
    <!-- global date format override -->
    <!-- defaults to yyyy-MM-dd -->
    <dateFormat>yyyy-MM-dd</dateFormat>
    
    <!-- global time format override -->
    <!-- defaults to HH:mm:ss -->
    <timeFormat>HH:mm:ss</timeFormat>


    <!-- custom javascript -->
    <scripts>
      <![CDATA[
        $(document).ready(function() {
          
        });
      ]]>
    </scripts>
    
    <!-- custom styles -->
    <styles>
      <![CDATA[
        
      ]]>
    </styles>
  </configuration>
</extentreports>

This ways we can configure the report information and can generate the extent reports.

Output of the above program is:

Please watch the YouTube video of this blog for better understanding.

The post Generating Extent Reports – CSharp appeared first on Selenium Webdriver Appium Complete Tutorial.

In software test automation after completion of the test suite execution we need to have a report for the execution status and it is the only way of evidence for the pass and fail status of the tests. And most of the clients bother about the detailed report of the execution status. Most of the licensed automation testing tools will have in built rich report option to show the execution status.

But coming to open source automation tools lacking in this option. Same way, Selenium also does not have the automation report generation option. But to execute the test suite, selenium is depending on unit testing frameworks like NUnit and MSTest.

After test suite execution using NUnit or MSTest, by default they will NOT give any HTML reports, If you want to generate HTML reports need to depend on other third party tools like NANT. But they will not give rich reports as the information is not that eye catchy.

To overcome these type of issues, we can use Extent Reports. These are very good and rich HTML reports. By using these reports we can provide lot information to the reports. These will also give the status in the form of PIE Chart.




Below are the advantages provided by the Extent Reports:

1. Status will be shown in the form of PIE chart.
2. Can replace the existing report with the new report or append the new status to the existing report.
3. We can change display order of the tests(i.e. oldest test at the top, newest at the end or newest test at the top, oldest at the end)
4. Can generate ONLINE or OFFLINE reports.
5. Can give the our own name to the test method (i.e can change the test method name in the report).
6. Can generate stepwise log information in the report.
7. Can segregate the tests using Test Categories.
8. Can give test author name to display in the report.
9. Can add a test node as a child of another test.
10. Can insert any custom HTML in the logs by using an HTML tag.
11. Can show the screenshots in the report wherever we need.
12. Can add recording of your test runs in the report.
13. Can add our own information in the report (i.e. version of selenium used, Environment information where the test suite executed).
14. Can give our own name to the HTML report.
15. It will give the System information in the report (i.e. HostName and OS used to execute the test suite.)

The above are the advantages provided by the extent reports. We can discuss all these things in the coming blogs.

Extent Report:

You can find the complete information in the below link:

http://extentreports.relevantcodes.com/net/

You can download the Extent Reports DLLs in this link:

http://extentreports.relevantcodes.com/

Apart from the above link, you can directly download using Nuget packages from Visual Studio.

Last but not least, a big thanks to Anshoo Arora for giving this type of reports.

Please watch the YouTube video of this blog for better understanding.

The post Extent Reports Introduction – CSharp appeared first on Selenium Webdriver Appium Complete Tutorial.