Settings ReportSettings/en

Aus expecco Wiki (Version 2.x)
Zur Navigation springen Zur Suche springen

Introduction[Bearbeiten]

This dialog is used to define the "Default Report Template", which is used if no customized report template has been selected (these might be present as attachment in the suite). The details of how templates affect the generated report are described in the "Report Template Attachment Editor" document.

Notice, that most customers will probably add testsuite-specific report templates for both a management overview report and a developer detail report as attachments to a suite, and generate reports for both via command line arguments or as test run parameter when automated via expeccoALM. So this default template is typically used as an ad-hoc template during test development.

Report Settings[Bearbeiten]

Always Use these Report Settings (vs. those from the Testsuite)[Bearbeiten]

Defines which the report template and which settings are to be used by the report generator. If disabled, the template and settings as specified in the testsuite or in the testplan are used for printing. If enabled, the one and only "Default Report Template" is used (which is remembered in the user's private settings).

Output Format(s)[Bearbeiten]

Specifies the output formats to be generated when this "Default Report Template" is used. For each enabled output format, an individual report file will generated. The set of supported output formats may depend on the expecco version and possibly the set of loaded and licensed plugins.

Currently, the following formats are always supported:

  • PDF - generates a PDF document
  • HTML - generates an HTML document, which could be published in a web-site
  • XML - generates an XML document in expecco's own XML format. This is a relatively comprehensive format, which includes a lot of the activity trace, pin values etc. For most real world reports, this level of detail is not needed, and the JUnit compatible XML format (see below) is sufficient.
  • CSV - generates a report in CSV format which can be imported into excel or a word document.
  • TEXT - generates a very simple text-only format (which could be piped to another (Unix-) command for post processing.
  • JUnit - generates an XML document which is compatible to the output format as generated by the Java JUnit testing framework. This is supported by many quality- and project management systems, and as such well supported by other tools.
    For example, it can be directly imported and processed by Jenkins (Hudson) to generate statistics, trends and project improvement reports.
    The XML schema is described eg. in "https ://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd".
  • Polarion Conform - same as the JUnit-XML format, except for the date- and time format, which used to be slightly different in some (older) Polarion versions. This may be obsolete with most recent Polarion releases.

Notice that especially the XML output formats can of course be further postprocessed (by e.g. XSLT processors) to generate customer specific report formats.

Report Language[Bearbeiten]

Specify the language (english, german,...), used for the report when using the "Default Report Template".

Edit Default Report Template[Bearbeiten]

Opens the "Report Template Editor" on the "Default Report Template".

Output Directory[Bearbeiten]

Specifies the directory (file folder), where the output files are to be generated.

Default Report Template[Bearbeiten]

Reset initial State[Bearbeiten]

Reset settings of the default report template to its initial values (as initially deployed).

Output Directory[Bearbeiten]

Define the output directory, where report files are generated. By default a temporary folder is used which is removed when expecco is terminated (this is not effective, if reports are generated via command line options).



Copyright © 2014-2024 eXept Software AG