Creating custom HTML/XML/Junit reports

Via the run log QF-Test provides a detailed log about the actions it executed during a test run. The overall results of this run log can be summarized in other reports like the HTML/XML/Junit report.

A not well documented – but gladly used – feature is that it is possible to adapt/change the style/content of these reports to the own needs. Nevertheless, in order to do so, basic programming knowledges are inevitably needed.

The HTML/XML/Junit reports are customizable. So the content of the “name” and “package” attribute can get changed.

The HTML/XML/JUnit-Reports are generated via an XSLT-Transformation. The therefore needed XSLT-Sheets are located in the directory

\qftest\qftest-$(version)\report.

If you are changing these Sheets, you may want to copy/move them to

\qftest\report.

As the XSLT-Transformation-Sheets in this directory are preferred over the XSLT-Transformation-Sheets in the \qftest\qftest-$(version)\report directory. Thus, your modified XSLT-Sheets will then also be used by later QF-Test versions. However – as an disadvantage – whenever a new QF-Test version is coming out with any XSLT-Sheets improvements, you will not notice these improvements anymore (as QF-Test will keep using the Sheets in the \qftest\report directory).

Notes

The XSLT Identity Transformation may be used in order to get the original XML Document out of which the HTML/XML/JUnit-Reports are getting generated:

<xsl:stylesheet version="1.0"  
 xmlns:xsl="http://www.w3.org/1999/XSL/Transform">  
  <xsl:template match="@*|node()">  
    <xsl:copy>  
      <xsl:apply-templates select="@*|node()"/>  
    </xsl:copy>  
  </xsl:template>  
 </xsl:stylesheet>

When generating an HTML report, you may want that QF-Test copies additional files (like additional JavaScript or stylesheet files) into the generated target directory. It is possible to inform QF-Test about such files. Therefore one simply creates a file with the name ‘files-to-copy.txt’. In this text file the additional JavaScript, stylesheet or image files are specified. (One file by line.)

We use "Matomo" cookies to anonymously evaluate your visit to our website. For this we need your consent, which is valid for twelve months.

Cookie Configuration

Functional cookies

We use functional cookies to ensure the basic functionality of the website.

Performance and statistics cookies

We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.

Cookie details
Description Vendor Lifetime Type Purpose
_pk_id Matomo 13 Months HTTP Contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.
_pk_ref Matomo 6 Months HTTP Used to track from which website the anonymized user proceeded to our website.
_pk_ses Matomo 1 Day HTTP The Matomo session cookie is used to track the visitor's page requests during the session.
_pk_testcookie Matomo Session HTTP Used to check whether the visitor's browser supports cookies.
_pk_cvar Matomo 30 Minutes HTTP Temporarily store data about the visit.
_pk_hsr Matomo 30 Minutes HTTP Temporarily store data about the visit.