Report Generation/en - Versionsgeschichte

Cg: /* Adding Additional Info at the Top */

2025-02-21T16:28:27Z

Adding Additional Info at the Top

← Nächstältere Version		Version vom 21. Februar 2025, 16:28 Uhr
Zeile 315:		Zeile 315:

	= Adding Additional Info at the Top =		= Adding Additional Info at the Top =
	[[Datei:SutVersionPlusExtraInfo.png\|~~mini~~]]		[[Datei:SutVersionPlusExtraInfo.png\|200px\|thumb\|Extra Info plus SUT Info]]
	Additional infos can be added to the top of the report. Typically, these will be version/release infos from the tested system (SUT or DUT).		Additional infos can be added to the top of the report. Typically, these will be version/release infos from the tested system (SUT or DUT).
	For this, specify an action block in the projects "Misc" page under "SUT Version Extract" action. This action block should provide an ordered collection containing key-value pairs.		For this, specify an action block in the projects "Misc" page under "SUT Version Extract" action. This action block should provide an ordered collection containing key-value pairs.
Zeile 321:		Zeile 321:
	An example is found in the examples folder under "d64_SUT_VersionInReport.ets".		An example is found in the examples folder under "d64_SUT_VersionInReport.ets".
	or (if only the explicit SUT info is to be shown):		or (if only the explicit SUT info is to be shown):
	[[Datei:SutVersionOnlyInfo.png\|~~mini~~]]		[[Datei:SutVersionOnlyInfo.png\|200px\|thumb\|SUT Info Only]]

	An example for a version extractor action (in JavaScript) looks like:		An example for a version extractor action (in JavaScript) looks like:

Cg: /* Adding Additional Info at the Top */

2025-02-21T16:27:23Z

Adding Additional Info at the Top

← Nächstältere Version		Version vom 21. Februar 2025, 16:27 Uhr
Zeile 315:		Zeile 315:

	= Adding Additional Info at the Top =		= Adding Additional Info at the Top =
		⚫	[[Datei:SutVersionPlusExtraInfo.png\|mini]]
	Additional infos can be added to the top of the report. Typically, these will be version/release infos from the tested system (SUT or DUT).		Additional infos can be added to the top of the report. Typically, these will be version/release infos from the tested system (SUT or DUT).
	For this, specify an action block in the projects "Misc" page under "SUT Version Extract" action. This action block should provide an ordered collection containing key-value pairs.		For this, specify an action block in the projects "Misc" page under "SUT Version Extract" action. This action block should provide an ordered collection containing key-value pairs.
	Typically, this would be an OrderedDictionary.		Typically, this would be an OrderedDictionary.
	An example is found in the examples folder under "d64_SUT_VersionInReport.ets".		An example is found in the examples folder under "d64_SUT_VersionInReport.ets".
		⚫	or (if only the explicit SUT info is to be shown):
		⚫	[[Datei:SutVersionOnlyInfo.png\|mini]]

	An example for a version extractor action (in JavaScript) looks like:		An example for a version extractor action (in JavaScript) looks like:
Zeile 334:		Zeile 337:
	versionOutput.value(info);		versionOutput.value(info);
	}		}

	and the output in the report will then be:
⚫	[[Datei:SutVersionPlusExtraInfo.png\|mini]]
⚫	or (if only the explicit SUT info is to be shown):
⚫	[[Datei:SutVersionOnlyInfo.png\|mini]]

Cg: /* Adding Additional Info at the Top */

2025-02-21T16:26:41Z

Adding Additional Info at the Top

← Nächstältere Version		Version vom 21. Februar 2025, 16:26 Uhr
Zeile 314:		Zeile 314:
	Similar to the above strategy, start PDF generation in a pre-action, collect data during the run and write the final PDF in a post-action at the end.		Similar to the above strategy, start PDF generation in a pre-action, collect data during the run and write the final PDF in a post-action at the end.

	== Adding Additional Info at the Top ==		= Adding Additional Info at the Top =
	Additional infos can be added to the top of the report. Typically, these will be version/release infos from the tested system (SUT or DUT).		Additional infos can be added to the top of the report. Typically, these will be version/release infos from the tested system (SUT or DUT).
	For this, specify an action block in the projects "Misc" page under "SUT Version Extract" action. This action block should provide an ordered collection containing key-value pairs.		For this, specify an action block in the projects "Misc" page under "SUT Version Extract" action. This action block should provide an ordered collection containing key-value pairs.

Cg: /* Adding Additional Info at the Top */

2025-02-21T16:21:07Z

Adding Additional Info at the Top

← Nächstältere Version		Version vom 21. Februar 2025, 16:21 Uhr
Zeile 336:		Zeile 336:

	and the output in the report will then be:		and the output in the report will then be:
			[[Datei:SutVersionPlusExtraInfo.png\|mini]]
			or (if only the explicit SUT info is to be shown):
			[[Datei:SutVersionOnlyInfo.png\|mini]]

Cg: /* Generating a PDF Report */

2025-02-21T16:19:54Z

Generating a PDF Report

← Nächstältere Version		Version vom 21. Februar 2025, 16:19 Uhr
Zeile 313:		Zeile 313:
	As part of the expecco installation, a PDF generator library is provided, which contains building blocks for PDF documents.		As part of the expecco installation, a PDF generator library is provided, which contains building blocks for PDF documents.
	Similar to the above strategy, start PDF generation in a pre-action, collect data during the run and write the final PDF in a post-action at the end.		Similar to the above strategy, start PDF generation in a pre-action, collect data during the run and write the final PDF in a post-action at the end.

			== Adding Additional Info at the Top ==
			Additional infos can be added to the top of the report. Typically, these will be version/release infos from the tested system (SUT or DUT).
			For this, specify an action block in the projects "Misc" page under "SUT Version Extract" action. This action block should provide an ordered collection containing key-value pairs.
			Typically, this would be an OrderedDictionary.
			An example is found in the examples folder under "d64_SUT_VersionInReport.ets".

			An example for a version extractor action (in JavaScript) looks like:

			execute() {
			var info = new OrderedDictionary;

			info["SUT version"] = "x.y.z";
			info["SUT releaseDate"] = Date.today();
			info["SUT user"] = OperatingSystem.getLoginName();
			info["A"] = "more info A";
			info["B"] = "more info B";
			info["C"] = "more info C";

			versionOutput.value(info);
			}

			and the output in the report will then be:

Cg: /* Testsuite */

2025-02-21T16:13:07Z

Testsuite

← Nächstältere Version		Version vom 21. Februar 2025, 16:13 Uhr
Zeile 63:		Zeile 63:

	==== Testsuite ====		==== Testsuite ====
	*'''~~Do not~~ Print Testsuite Environment'''<br>This option determines whether the testsuite environment, i.e. the variables defined in the current testsuite, are part of the test report. Please note that only variables which are defined as read-only will be shown in the report because the value of other variables can change during the test execution.		*'''Print Testsuite Environment'''<br>This option determines whether the testsuite environment, i.e. the variables defined in the current testsuite, are part of the test report. If on, those are printed as a table ner the top of the report. Please note that only variables which are defined as read-only will be shown in the report because the value of other variables can change during the test execution.

			*'''Print Execution Info'''<br>This option determines whether additional info about the operating system, cpu type, host and user name are printed in a table near the top of the report. Unless disabled by the flag below, this also includes any infos whic hwere explicitly generated by the "SUT Version Info" action as specified in the suite's "misc" section.

			*'''Only Print SUT Info'''<br>If checked, only the explicit info is printed, and any internally generated host, os and cpu infos are suppressed.

	==== Testplan ====		==== Testplan ====

Cg: /* Automatic Report Generation */

2025-02-21T11:00:33Z

Automatic Report Generation

← Nächstältere Version		Version vom 21. Februar 2025, 11:00 Uhr
Zeile 6:		Zeile 6:
	The full detail XML contains all data as collected during the run, including timestamps and input-/output values of every logged activity. By using XML and a processor such as XSLT, any custom report can be generated from it, if the other reports are not sufficient.		The full detail XML contains all data as collected during the run, including timestamps and input-/output values of every logged activity. By using XML and a processor such as XSLT, any custom report can be generated from it, if the other reports are not sufficient.

	In addition, you can also save an ".elf" file (which stands for "''expecco log file''").		In addition, you can also save a ".elf" file (which stands for "''expecco log file''").
	This can later be reopened with expecco, to present the same view as after the run (i.e. the whole hierarchical execution trace is shown). Then, the test can be reexecuted or additional reports can be generated (possibly with different detail settings).		This can later be reopened with expecco, to present the same view as after the run (i.e. the whole hierarchical execution trace is shown). Then, the test can be reexecuted or additional reports can be generated (possibly with different detail settings).

Cg: /* How to Customize a Report Template */

2025-02-21T09:55:47Z

How to Customize a Report Template

← Nächstältere Version		Version vom 21. Februar 2025, 09:55 Uhr
Zeile 56:		Zeile 56:

	== How to Customize a Report Template ==		== How to Customize a Report Template ==
	To customize a report template, select it in the navigation tree. The same editor is used as when modifying the default report template (which is found in "''Extras''" → "''Report''" → "''Default Report Template''".		To customize a report template, select it in the navigation tree. The same editor is used as when modifying the default report template (which is found in "''Extras''" → "''Report''" → "''Default Report Template''").

	=== Filter Settings ===		=== Filter Settings ===

Cg: /* How to Customize a Report Template */

2025-02-21T09:55:30Z

How to Customize a Report Template

← Nächstältere Version		Version vom 21. Februar 2025, 09:55 Uhr
Zeile 56:		Zeile 56:

	== How to Customize a Report Template ==		== How to Customize a Report Template ==
	To customize a report template, select it in the navigation tree. The same editor is used as when modifying the default report template.		To customize a report template, select it in the navigation tree. The same editor is used as when modifying the default report template (which is found in "''Extras''" → "''Report''" → "''Default Report Template''".

	=== Filter Settings ===		=== Filter Settings ===

Cg: /* How to create a report */

2025-02-21T09:49:21Z

How to create a report

← Nächstältere Version		Version vom 21. Februar 2025, 09:49 Uhr
Zeile 18:		Zeile 18:
	[[Bild:Report Settings.png\|thumb\|200px\|Report Settings]]		[[Bild:Report Settings.png\|thumb\|200px\|Report Settings]]
	To create a report, a test has to be executed first (or a ".elf" file be loaded from a previous run).		To create a report, a test has to be executed first (or a ".elf" file be loaded from a previous run).
	This can be either a single block test or a whole testplan. After the execution is finished, click on the "''Print report''" button ([[Bild:Icon Print Report.png\|Report button]]) causing a dialog to open.		This can be either a single block test or a whole testplan. After the execution is finished, click on the "''Print report''" button ([[Bild:Icon Print Report.png\|Report button]]) causing a dialog to open (reports can also be created automatically via [[Starting_expecco_via_Command_Line/en#Reporting\|command line arguments]] without user interaction).

	Select the output format (PDF, HTML, XML, CSV or TEXT), the report language, a paper format and a template for the report. This template can be the default report template, a template from the current testsuite or a template which is stored separately in a file. You can also make ad-hoc changes to the printed report right before it is generated, by clicking on "''Edit Default Report Template''" in the 'Generate Report' dialog. There, you can specify the detail and the look of the report (depth, detail, filter, company, logos, colours, fonts, etc.).		Select the output format (PDF, HTML, XML, CSV or TEXT), the report language, a paper format and a template for the report. This template can be the default report template, a template from the current testsuite or a template which is stored separately in a file. You can also make ad-hoc changes to the printed report right before it is generated, by clicking on "''Edit Default Report Template''" in the 'Generate Report' dialog. There, you can specify the detail and the look of the report (depth, detail, filter, company, logos, colours, fonts, etc.).