Settings ReportSettings/en - Versionsgeschichte

Cg am 28. Juni 2024 um 10:27 Uhr

2024-06-28T10:27:38Z

← Nächstältere Version		Version vom 28. Juni 2024, 10:27 Uhr
Zeile 5:		Zeile 5:

	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.		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.

			You find these under "''Extras''" → "''[[Settings/en\|Settings]]''" → "''Report''".

	== Report Settings ==		== Report Settings ==

Cg: /* Output Format(s) */

2021-07-05T16:28:56Z

Output Format(s)

← Nächstältere Version		Version vom 5. Juli 2021, 16:28 Uhr
Zeile 21:		Zeile 21:

	Currently, the following formats are always supported:		Currently, the following formats are always supported:
	* PDF - generates a PDF document		* '''PDF''' - generates a PDF document
	* HTML - generates an HTML document, which could be published in a web-site		* '''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.		* '''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.		* '''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.		* '''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.<br>For example, it can be directly imported and processed by Jenkins (Hudson) to generate statistics, trends and project improvement reports.<br>The XML schema is described eg. in [https://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd "https ://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd"].		* '''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.<br>For example, it can be directly imported and processed by Jenkins (Hudson) to generate statistics, trends and project improvement reports.<br>The XML schema is described eg. in [https://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd "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.		* '''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.		Notice that especially the XML output formats can of course be further postprocessed (by e.g. XSLT processors) to generate customer specific report formats.

Cg: /* Output Format(s) */

2021-07-05T16:28:25Z

Output Format(s)

← Nächstältere Version		Version vom 5. Juli 2021, 16:28 Uhr
Zeile 26:		Zeile 26:
	* CSV - generates a report in CSV format which can be imported into excel or a word document.		* 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.		* 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.<br>For example, it can be directly imported and processed by Jenkins (Hudson) to generate statistics, trends and project improvement reports.		* 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.<br>For example, it can be directly imported and processed by Jenkins (Hudson) to generate statistics, trends and project improvement reports.<br>The XML schema is described eg. in [https://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd "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.		* 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.

Emi am 14. Januar 2021 um 08:30 Uhr

2021-01-14T08:30:37Z

← Nächstältere Version		Version vom 14. Januar 2021, 08:30 Uhr
Zeile 42:		Zeile 42:

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

			= Default Report Template =
			== Reset initial State ==
			Reset settings of the default report template to its initial values (as initially deployed).

			= Output Directory =
			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).

	[[Category:Settings]]		[[Category:Settings]]

Cg: /* Introduction */

2019-02-22T15:01:53Z

Introduction

← Nächstältere Version		Version vom 22. Februar 2019, 15:01 Uhr
Zeile 1:		Zeile 1:
	== Introduction ==		== Introduction ==
	This dialog is used to define the ~~default~~ ~~report~~ ~~template~~,		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).		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 [[ReportTemplateAttachment_Editor/en \| "Report Template Attachment Editor"]] document.		The details of how templates affect the generated report are described in the [[ReportTemplateAttachment_Editor/en \| "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 ==		== Report Settings ==

Cg: /* Use Report Settings from Testsuite */

2019-02-22T14:58:00Z

Use Report Settings from Testsuite

← Nächstältere Version		Version vom 22. Februar 2019, 14:58 Uhr
Zeile 6:		Zeile 6:
	== Report Settings ==		== Report Settings ==

	=== Use Report Settings from Testsuite ===		=== Always Use these Report Settings (vs. those from the Testsuite) ===

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

	=== Output Format(s) ===		=== Output Format(s) ===

Cg: /* Output Directory */

2019-02-22T14:56:13Z

Output Directory

← Nächstältere Version		Version vom 22. Februar 2019, 14:56 Uhr
Zeile 39:		Zeile 39:
	=== Output Directory ===		=== Output Directory ===

	~~Select~~ the directory, where the ~~outputs~~ ~~generated~~ by ~~the~~ ~~report~~ ~~generator are stored~~.		Specifies the directory (file folder), where the output files are to be generated.

	[[Category:Settings]]		[[Category:Settings]]

Cg am 22. Februar 2019 um 14:55 Uhr

2019-02-22T14:55:40Z

← Nächstältere Version		Version vom 22. Februar 2019, 14:55 Uhr
Zeile 2:		Zeile 2:
	This dialog is used to define the default report template,		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).		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 [[ReportTemplateAttachment_Editor/en \| Report Template Attachment Editor]].		The details of how templates affect the generated report are described in the [[ReportTemplateAttachment_Editor/en \| "Report Template Attachment Editor"]] document.

	== Report Settings ==		== Report Settings ==
Zeile 35:		Zeile 35:
	=== Edit Default Report Template ===		=== Edit Default Report Template ===

	Opens the Report Template Editor on the "''Default Report Template''".		Opens the [[ReportTemplateAttachment_Editor/en \| "Report Template Editor"]] on the "''Default Report Template''".

	=== Output Directory ===		=== Output Directory ===

Cg: /* Edit Default Report Template */

2019-02-22T14:55:05Z

Edit Default Report Template

← Nächstältere Version		Version vom 22. Februar 2019, 14:55 Uhr
Zeile 35:		Zeile 35:
	=== Edit Default Report Template ===		=== Edit Default Report Template ===

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

	=== Output Directory ===		=== Output Directory ===

Cg: /* Report Language */

2019-02-22T14:54:41Z

Report Language

← Nächstältere Version		Version vom 22. Februar 2019, 14:54 Uhr
Zeile 31:		Zeile 31:
	=== Report Language ===		=== Report Language ===

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

	=== Edit Default Report Template ===		=== Edit Default Report Template ===