Community
Participate
Working Groups
If a verdict event was caused by a bunch of other verdict events, currently the editor provides a link "Go To First Problem". There is no way to locate the other problems that caused this verdict although in the model, there might be a list of such events. Suggestions: #1: Provide a list of all causing events as hyperlinks. Also nice to have a way to navigate back to the caused event. Understand that the list could be huge. #2: Provide a button instead of the list of links that when clicked will list all the causing events in the search window. Click on each entry in th esearch window to navigate to that event in th eexecution history editor. Also provide a button in the search window to navigate back to the caused event. #3: Any other way? My personal preference is #2.
OK for #2
Should we tie the verdicts into the problems view in any way? For example, if I click on one execution history based on my filter set-up, the problems view could display fail verdicts for that one execution. If my filters are set-up to include the entire project it might list all the fail verdicts for the entire project of executions. Is this possible, advisable, cool, an entirely different enhancement request or anything else? As users fix the problems in their code and re-run their tests, the problem list will shrink since they have resolved the failure into a pass verdict. Another reason I like this is because it is a standard Eclipse approach for displaying errors, warnings and info, etc. I'm not sure if this idea overlaps this enhancement request or is another one altogether. It seems like it might overlap this one although perhaps the problems view and search view solutions could co-exist?
Need UI modification => 4.1
Targeting to 4.2 and assigning to current Test.UI component owner.
Reassigning to Bianca for tptp 4.2.
Agreed by Ashish this is an enhancement rather than a defect since this feature was not available in Test Log Viewer before. Ashish, please feel free to adjust the Priority properly for future release planning.
Updating target to future as requested by the PMC. Enhancements are targeted to future if not in plan for the current release.
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).
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 enhancement/defect has been resolved and unverified for more than 1 year 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.
