ATU Reporter Part 4

Customizing the Reports:

This Section describes how to modify some parts of the Reports as per the user requirement. This is supported from version 3.0 or above.

Version 3.0 :

Following are the customization's that you can do with the reports.

• Set a Title of the Project in the Reports Header Section.
• Add a logo of your choice that will appear at the right side of the header section
• Log reports of your choice: 

         Ex: ATUReports.add("<a href=\"#\">My Logs using ATU Reporter</a>", true);
         or
              Reporter.log("<a href=\"#\">My Logs using TestNG Reporter</a>");
              These reports will appear in the test case report as a link.

• Change the directory of the Reports folder (Name of the folder will be user's choice)
• Description of the Project on Index page

The customization's are pulled from an external properties file having key value pairs. The property file keys would be as follows.

#change results directory

atu.reports.dir=D:/ATU Reporter

#change header text

atu.proj.header.text=My Proj Reports

#add project/client logo, the image is copied to "HTML_Design_Files/IMG" directory

atu.proj.header.logo=D:/google.png


#specify your project description

atu.proj.description=MyProject Testing Reports

Version 4.0 :

Following are the customization's that you can do with the reports.

#An option for the user to set whether screenshots should be taken or not regardless of what the user has logged in the script. Setting false for taking screenshots results in faster execution time. This option is best suitable when you use HtmlUnitDriver
atu.reports.takescreenshot=false

#User has the option to choose whether configuration reports should be generated or not
atu.reports.configurationreports=false



#generate excel reports - the first preview of excel reports - with noticeable limitations
#excel reports rely on external libraries - Visit ATU Reporter Part 5 Post  for External Dependencies - These are required
atu.reports.excel=true

#generate pdf reports, not yet implemented
atu.reports.pdf=false

Once the properties file has been defined. you have to set a System property that will point to the properties file.  This property must be defined within a static block in the Test Script as shown below
Ex:

@Listeners({ ATUReportsListener.class, ConfigurationListener.class, MethodListener.class })

public class SampleScript {

       {

              System.setProperty("atu.reporter.config", "D:\\atu.properties");

       }

       @Test

       public void loginTest() {

              // Code..

       }

}

Version 4.5 :

Following are the customization's that you can do with the reports

• Set the Test case Requirement coverage description using below code, this snippet must be called within a test method

      @Test

      public void login() {

      ATUReports.setTestCaseReqCoverage("This test is mapped to Login Requirement TC_001");

      //..

      }

• Set the Current run description using below code, this declaration can be done in any block

      ATUReports.currentRunDescription = "This is a Test Run";

• Filter the test case in Current Run Page

Version 5.0 :

• Log a step as failed (using LogAs parameter). you can continue execution of the remaining steps using this property

          atu.reports.continueExecutionAfterStepFailed = false

• Record test execution - complete suite

          atu.reports.recordExecution=suite
          Note: Add "Test Execution Recorder" library to your class-path to record the execution. This is tested with VLC Player (The VLC plug-in must be enabled in the browser to play the video)

 

Once the above declaration is done, the ATUReporter will pick the defined properties from the file.
If there are multiple script files, then the above declaration can be done in any one of the Script.

We will be happy to hear your requests for new features. Let us know if any customizations are needed, we will check the feasibility and possibly implement that in the upcoming versions :). Any bugs you encounter, you can report us, we are always here, committed in resolving the bugs :)