Home » Archived » Test and Performance Tools Platform (TPTP) » TPTP & XML report improvement
|
| Re: TPTP & XML report improvement [message #91391 is a reply to message #91362] |
Wed, 17 January 2007 18:04   |
Eclipse User |
|
|
|
Originally posted by: bquenin.free.fr
Hi all,
I think that what Pierre means is that the TPTP reporting lacks some
important information. A testing tool (as TPTP) could be wonderful, it
won't be any use if it can't report things gracefuly and in a exhausting
way. I think that TPTP suffers from its reporting feature. Indeed, it's an
amazing tool, you can really do complex, in-depth testing with it but
everything collapse when you get the reporting point. The new BIRT based
test reports are better, but still lack some necessary information (like
test methods description, time slices, etc.).
It's possible to create its own report with BIRT and XML raw report but,
again, raw data lacks information ...
It becomes kinda difficult then to create a pertinent report, making the
choice to use TPTP as a test platform harder to justify ...
Perhaps I missed some information/documentation about reporting
features, if so, all apologies =) Anyway, TPTP is definitely a great
testing tool and then, it has to offer a great reporting =)
Any comments woud be greatly appreciated.
Regards.
BQ
|
|
|
| Re: TPTP & XML report improvement [message #91746 is a reply to message #91391] |
Wed, 24 January 2007 13:53 |
 Jonathan Brown
Messages: 22
Registered: July 2009 |
Junior Member |
|
|
For what it's worth, I don't bother with using TPTP for reporting - only for
execution.
I found it much more useful to write a simple hook for JUnit and then
persists test results to a MySQL db using hibernate once the tests complete.
This way I can persist whatever descriptive info I want to regarding a
particular test. This arrangement also allows me to drive my BIRT reports
off the test results database.
jb
"Bertrand Quenin" <bquenin@free.fr> wrote in message
news:f4686d7fd4c4568835133733ba317113$1@www.eclipse.org...
> Hi all,
>
> I think that what Pierre means is that the TPTP reporting lacks some
> important information. A testing tool (as TPTP) could be wonderful, it
> won't be any use if it can't report things gracefuly and in a exhausting
> way. I think that TPTP suffers from its reporting feature. Indeed, it's an
> amazing tool, you can really do complex, in-depth testing with it but
> everything collapse when you get the reporting point. The new BIRT based
> test reports are better, but still lack some necessary information (like
> test methods description, time slices, etc.).
> It's possible to create its own report with BIRT and XML raw report but,
> again, raw data lacks information ...
> It becomes kinda difficult then to create a pertinent report, making the
> choice to use TPTP as a test platform harder to justify ...
>
> Perhaps I missed some information/documentation about reporting features,
> if so, all apologies =) Anyway, TPTP is definitely a great testing tool
> and then, it has to offer a great reporting =)
>
> Any comments woud be greatly appreciated.
>
> Regards.
> BQ
>
>
>
>
|
|
|
| Re: TPTP & XML report improvement [message #96826 is a reply to message #91391] |
Tue, 24 April 2007 17:42 |
Paul Slauenwhite
Messages: 975
Registered: July 2009 |
Senior Member |
|
|
[Response from Sheldon Lee-Loy]
Hi Pierre and Bertrand,
In general, one of the main design issues to reporting is that each report
needs to work off a normalized model of the data. This normalized model can
be specialized for each type of report. For example one report might want to
show the test results executed on a particular day while another report
might want to show a pie chart with the number of passed and failed test
cases. When you consider supporting drill-down this adds another complexity
to the model the reports work off of.
The TPTP test reports work off a generic normalized xml stream. Currently
the xml schema that describes the xml is not documented . This is a current
issue that I am aware of(Bugzilla entry 145421 -
https://www.eclipse.org/bugs/show_bug.cgi?id=145421). The reason for this
xml stream is to create simple reports without knowing too much of the
structure of the EMF model.
For reports that can not be created using this generic normalized xml stream
there are extension points in place to normalize the Test model. The
following extension point is provided.
<extension
point="org.eclipse.tptp.platform.report.birt.reportElement"
id="org.foo.MyReportElement">
<reportElement
description="%TEST_PASS_REPORT_DESC"
name="%TEST_PASS_REPORT_NAME"
id="com.foo.ReportElementId"
class="com.foo.MyReportElement">
<classProperty name="CONTEXT_MSG_BUNDLE" class="com.foo.Messages"/>
<property name="CONTEXT_IMG_DIR" value="images"/>
<property name="CONTEXT_TEMPLATE_FILE"
value="templates/MyReport.rptdesign"/>
</reportElement>
</extension>
Where:
point - the report elemnet extension point
description - provides text to describe the report
name - the name of the report
id - a unique identifier
class - a
org.eclipse.tptp.platform.report.birt.core.provisional.IRepo rtElement class
that provides the datasource used by the report.
classProperty - A message bundle that contains the externalized strings.
property CONTEXT_IMG_DIR - the output directory to save image files
property CONTEXT_TEMPLATE_FILE - the BIRT report template file to use. Note
this is optional if your IReportElement class specifies the report template
file already.
IReportElement provides the necessary information needed by the report
generator to create static html reports. A report element is composed of
essential three parts:
datasource - an input stream that contains the raw data to generate the
report. Note the type of datasource (ie. xml, csv, etc) should be the
expected data source needed by the report template file. The developer
should have an understanding of the EMF test model.
template file - the BIRT template file that contains the cosmetic
information and layout information of the report.
output stream - the stream to write the resulting html text to.
If you want to add this new report to the report wizard you add the
following extension point:
<extension
point="org.eclipse.hyades.ui.reportGenerators">
<wizard
icon="icons/full/cview16/log_view.gif"
class=" org.eclipse.tptp.test.report.birt.ui.internal.GenericTestRep ortWizard "
description="%BIRT_MY_REPORT_DESC"
name="%BIRT_MY_REPORT_NAME"
id="com.foo.ReportElementId"/>
</extension>
where
point - is the report wizard extension point
icon - is the icon to show next to this report entry
class - the wizard class
description - the description to show in the wizard describing this report
name - the name of this report entry
id - the id that is associated with your report element.
Sheldon
"Bertrand Quenin" <bquenin@free.fr> wrote in message
news:f4686d7fd4c4568835133733ba317113$1@www.eclipse.org...
> Hi all,
>
> I think that what Pierre means is that the TPTP reporting lacks some
> important information. A testing tool (as TPTP) could be wonderful, it
> won't be any use if it can't report things gracefuly and in a exhausting
> way. I think that TPTP suffers from its reporting feature. Indeed, it's an
> amazing tool, you can really do complex, in-depth testing with it but
> everything collapse when you get the reporting point. The new BIRT based
> test reports are better, but still lack some necessary information (like
> test methods description, time slices, etc.).
> It's possible to create its own report with BIRT and XML raw report but,
> again, raw data lacks information ...
> It becomes kinda difficult then to create a pertinent report, making the
> choice to use TPTP as a test platform harder to justify ...
>
> Perhaps I missed some information/documentation about reporting features,
> if so, all apologies =) Anyway, TPTP is definitely a great testing tool
> and then, it has to offer a great reporting =)
>
> Any comments woud be greatly appreciated.
>
> Regards.
> BQ
>
>
>
>
|
|
|
Goto Forum:
Current Time: Fri Apr 26 14:31:16 GMT 2024
Powered by FUDForum. Page generated in 0.03399 seconds |
] 
Search
Help
Register
Login
Home
