Community
Participate
Working Groups
Provide simple accumulative verdict summary results reporting. When executing more than one test suite, there is no mechanism to create even simple verdict summary results reports on one or more test suite execution results files. An organized approach to product testing would typically include multiple testers running multiple test suites in parallel. Core administrative functions of such a test run would require simple accumulative verdict summary results reporting (e.g. pass/failure/total cases). Reporting could be graphical (e.g. SVG) or simply textual (e.g. tabular).
Created attachment 16079 [details] Tabular Verdict Summary Report Generator
Enclosed is an implementation of a simple tabular verdict summary report Generator. Reports are generated by the user selecting a test suite. All execution results for the selected test suite and all (recursively) referenced test suites are formatted into a tabular verdict summary test report. Reports are generated for a finite period of time, called a report window. The report window consists of a start date and time and an end date and time (UTC). The window is used to resolve execution results for a test suite within a finite period of time. The following execution result information is captured in the tabular verdict summary test report: -Suite -Pass -Fail -Error -Inconclusive -Attempted -Total -Completion Rate -Failure Rate </ul> Furthermore, each test suite is expandable to display the following execution result information: <ul> -Case -Verdict -Comment </ul> If any type of error occurs during report generation, an error HTML page is generated instead. The error HTML page indicates the source of the error in the form of a stack trace.
The enclosed implementation of a simple tabular verdict summary report generator requires enhancement #79181 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=79181 ).
Created attachment 16454 [details] Tabular Summary Report Generator
Enclosed is an implementation of a simple tabular summary report Generator. Reports are generated by the user selecting a test suite. All (recursively) referenced test suites and all execution results for the selected and each referenced test suite are formatted into a tabular summary test report. Reports are generated for a finite period of time, called a report window. The report window consists of a start date and time and an end date and time (UTC). The window is used to resolve execution results for a test suite within a finite period of time. The following execution result information is captured in the tabular verdict summary test report: -Suite -Pass -Fail -Error -Inconclusive -Attempted -Total -Completion Rate -Failure Rate </ul> Furthermore, each test suite is expandable to display the following execution result information: <ul> -Case -Verdict -Comment </ul> If any type of error occurs during report generation, an error HTML page is generated instead. The error HTML page indicates the source of the error in the form of a stack trace.
*** Bug 63144 has been marked as a duplicate of this bug. ***
Required plugins for the attached generators include: <import plugin="org.eclipse.ui"/> <import plugin="org.eclipse.core.runtime"/> <import plugin="org.eclipse.core.resources"/> <import plugin="org.eclipse.hyades.models.common"/> <import plugin="org.eclipse.hyades.ui"/> <import plugin="org.eclipse.hyades.test.ui"/>
Hi, Could you target this enhancement to an iteration, please? Thanks, Ruth.
Both the Tabular Summary Report Generator and Tabular Verdict Summary Report Generator have been migrated into one generator called the Tabular Verdict Summary Report Generator for ease of use and maintenance. Please use the latest Tabular Verdict Summary Report Generator (Feb 17, 2005) for this feature.
Created attachment 18065 [details] Tabular Verdict Summary Report Generator
Is an 4.0 (i4) target realistic since this enhancement will require UI and documentation changes? I believe i2 is the last iteration for UI/documentation changes. Ruth, can you confirm?
*** Bug 83921 has been marked as a duplicate of this bug. ***
Iteration 2 is the last iteration for UI, doc, and API changes.
*** Bug 74803 has been marked as a duplicate of this bug. ***
targeted to i2 due to UI change
Fixed. New dependency on o.e.tptp.platform.report.core added.
Verified in Toronto's TPTP 4.0 200504050020 build (HEAD) on April 10, 2005. Excellent job! The new graphical 3-D reports are great!
Closing.
