Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 165792

Summary:	Test log viewer - Overview - Verdict List problems
Product:	z_Archived	Reporter:	Marius Slavescu <slavescu>
Component:	TPTP	Assignee:	Bozier jerome <jerome.bozier>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	paulslau
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	housecleaned460 closed460

Description Marius Slavescu

2006-11-24 10:45:07 EST

Here are some problems that I found using the Overview page from "Test log viewer" (which is actually an editor, this seems to a naming problem):

1. The Verdict Summary although draws the attention in the first place doesn't give a quick look of the overall verdict, to find that the user has to check which percentage is larger or look at the "Common Properties"->Verdict entry or look at the Verdict List where first time the overall verdict type is shown there.
Would be good to have a visual (graphical) cue that can quickly tells us the overall verdict.

2. The Verdict List shows the last 20 verdicts which is good, although the label used for the links doesn't give any information about where the verdict was generated, I think it would be much better to also show the "Element description" of the verdict element (see https://bugs.eclipse.org/bugs/attachment.cgi?id=54484&action=view for an example from Bug 165785).

The overall verdict event is the last one and that will not be directly accessible from overview if we have more then 20 verdicts of that type, would be good to have a separate link just for the overall verdict which could be accessed through the visual cue proposed in problem 1.

Comment 1 Harm Sluiman

2006-11-24 15:52:55 EST

marius this seems like a samll enhancement request. Please work with Paul to move it to 4.4

Comment 2 Marius Slavescu

2006-11-24 16:06:35 EST

I agree, I meant it to be an enhancement. 

Paul please change the priority accordingly.

Another quick improvement can be done on the Events page, initially by using more meaningfully labels in the "Events" tree (use the content shown in "Element description" plus some prefix/postfix where needed) and later using a filtering capability in that tree with options like show only "invocation" type nodes and somehow combine the messages in the "Text" field, that way we can quickly look at the results without the need to expand 3 levels to see the error/failure messages.

Comment 3 Mark D Dunn

2006-11-27 11:11:01 EST

Reassign to Bianca. Bianca handles Test Log issues.

Comment 4 Paul Slauenwhite

2006-11-27 12:04:21 EST

These are valid improvement's for the Test Log Viewer.  

Adjusting priority to include as a 4.4 candidate.

Comment 5 Bianca Jiang

2006-11-27 14:52:54 EST

(In reply to comment #2)
> I agree, I meant it to be an enhancement. 
> 
> Paul please change the priority accordingly.
> 
> Another quick improvement can be done on the Events page, initially by using
> more meaningfully labels in the "Events" tree (use the content shown in
> "Element description" plus some prefix/postfix where needed) and later using a
> filtering capability in that tree with options like show only "invocation" type
> nodes and somehow combine the messages in the "Text" field, that way we can
> quickly look at the results without the need to expand 3 levels to see the
> error/failure messages.
> 

The Event labels are extensible. There's an extension point where extenders can use to customize the icon and display text of the events. There is a default label provider if such an extender doesn't exist. Based on the event type, the default label provider displays different attributes of the event. For example, it uses label attribute for verdict events and the name of the interactionFragment for loop events.

For filtering, there is an existing enhancement request on this: bug 108527. Before that's implemented, the test log viewer Search function (bug 89341) can be used to help get a list of one or more specific types of event.

Comment 6 Paul Slauenwhite

2007-03-14 14:28:06 EDT

Updating target to future as requested by the PMC.  

Enhancements are targeted to future if not in plan for the current release.

Comment 7 Paul Slauenwhite

2007-11-05 12:00:13 EST

Correcting priority since not a 4.5 candidate enhancement (see http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html).

Comment 8 Paul Slauenwhite

2009-06-30 06:28:35 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).

Comment 9 Paul Slauenwhite

2009-06-30 06:50:33 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).

Comment 10 Paul Slauenwhite

2009-06-30 09:43:21 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.