Bug 155093 - Incorrect summary verdict when generating JScrib reports on test executions with no verdicts.
Summary: Incorrect summary verdict when generating JScrib reports on test executions w...
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Paul Slauenwhite CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 144045
Blocks:
  Show dependency tree
 
Reported: 2006-08-24 14:55 EDT by Paul Slauenwhite CLA
Modified: 2016-05-05 10:30 EDT (History)
3 users (show)

See Also:


Attachments
Test resources (14.06 KB, application/x-zip-compressed)
2006-08-24 14:55 EDT, Paul Slauenwhite CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Slauenwhite CLA 2006-08-24 14:55:05 EDT
Incorrect summary verdict when generating JScrib reports on test executions with no verdicts.

Using the enclosed test suite/execution, the JScrib reports generates a Pass summary verdict despite the default arbitrated verdict in the model being inconclusive.
Comment 1 Paul Slauenwhite CLA 2006-08-24 14:55:24 EDT
Created attachment 48627 [details]
Test resources
Comment 2 Joe Toomey CLA 2006-08-24 15:47:38 EDT
To be precise, a test log that is generated with no verdicts does not have an arbitrated verdict.  In all TPTP tests, the arbiter runs in the remote process (as part of the runner) and assigns arbitrated verdicts based on verdict events.  In the case described, inconclusive is not an arbitrated verdict.  It is a default value as defined in our EMF model.
Comment 3 Paul Slauenwhite CLA 2006-10-23 10:50:34 EDT
Please target to 4.4 and review the priority according to http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html.
Comment 4 Paul Slauenwhite CLA 2007-01-26 08:25:24 EST
Targeting to future since not containable in 4.4.
Comment 5 Paul Slauenwhite CLA 2007-01-26 09:01:34 EST
As discussed on this week's Test Project call (January 22, 2007), the Test Project will focus on existing P1 - P2/Blocker - Major and P1/Normal and test creation/automation defects (omitting defects dependant on outstanding features) in TPTP 4.4.  All other Test Project defects have been targeted to future.

If this defect has been targeted to future and you/originator feel it should be completed in 4.4, please provide the necessary reason as a reply to this comment or a post to the Test Project mailing list (tptp-test-tooling-dev@eclipse.org).  We will collectively triage and assess our resources to determine a case-by-case decision. 
Comment 6 Paul Slauenwhite CLA 2007-01-26 09:04:04 EST
Correction:  The Test Project mailing list is tptp-testing-tools-dev@eclipse.org.
Comment 7 Paul Slauenwhite CLA 2008-01-24 09:40:07 EST
The following files checked in to CVS (HEAD):

org.eclipse.hyades.test.tools.ui.common.internal.report.jscrib.JscribWriter.java
org.eclipse.hyades.test.tools.ui.common.internal.report.jscrib.ReportDataUtils.java
org.eclipse.tptp.test.samples.internal.resources.SamplesPluginResourceBundle.java
/org.eclipse.tptp.test.samples/src/org/eclipse/tptp/test/samples/internal/resources/messages.properties
Comment 8 Harm Sluiman CLA 2008-01-25 11:39:14 EST
(In reply to comment #7)
> The following files checked in to CVS (HEAD):
> 
> org.eclipse.hyades.test.tools.ui.common.internal.report.jscrib.JscribWriter.java
> org.eclipse.hyades.test.tools.ui.common.internal.report.jscrib.ReportDataUtils.java
> org.eclipse.tptp.test.samples.internal.resources.SamplesPluginResourceBundle.java
> /org.eclipse.tptp.test.samples/src/org/eclipse/tptp/test/samples/internal/resources/messages.properties
> 

This code became deprecated when we enable BIRT. It continued to be packaged for API compatibility only. It is not clear why we are fixing defects here.
Comment 9 Paul Slauenwhite CLA 2008-01-25 14:09:30 EST
(In reply to comment #8)
> This code became deprecated when we enable BIRT. It continued to be packaged
> for API compatibility only. It is not clear why we are fixing defects here.

The two JScrib report generators have never been deprecated, hence the fix.  

Comment 10 Paul Slauenwhite CLA 2008-02-12 09:58:58 EST
Verified in 4.5.0-200802100400.