Community
Participate
Working Groups
Users expect immmediate feedback as a test is executing. Users want the ability to see whether their test is running, some test results, to know if the test is following the appropriate path (e.g., is it running the script properly, is the test substituting data correctly?), etc. Many users expected to see this feedback in a separate view during test execution (e.g., at the bottom of the perspective). It should also be noted that the majority of users during some usability studies with performance testers, did not discover the execution log viewer. It was not obvious to users that they must locate the Execution object in the navigator, then open it in order to see any Execution feedback.
Targeting this as future, but design should start in 3.2
Interpreting this defect as a request to automatically open the execution history of a testt is launched (thus provding the user with the viual feedback.) Combined with 76858, this will open to the events tab, which shows the run progressing.
My thoughts were more on providing lighter-weight feedback than the current Execution History. Users want to quickly be able to see that the test is indeed running, URL is being invoked (where appropriate), datapool substitutions, etc. While the Execution History editor/view does provide this information, it is displayed as an Editor that requires a significant amount of navigation to find the required information. I had envisioned a small view similar to the Recorder Control view that displays feedback while recording at the bottom of the Test Perspective or similar to the Console view that is displayed when running a Java app in Eclipse (that has console output). There seems to be a number of possibilities: 1) providing a light-weight execution feedback view a the bottom of the Test Perspective. 2) display the Execution History (but work to improve the usability of the Execution History; does the Execution History view even update in real-time?) 3) Curtis, in Bug 83124, mentions the Eclipse jobs dialog to display feedback If appropriate we can discuss this bug in the next TPTP UI meeting.
*** Bug 83124 has been marked as a duplicate of this bug. ***
There is also a similar enhancement request with even more ideas/information (that I had entered in the past) [bugzilla_80330]
*** Bug 80330 has been marked as a duplicate of this bug. ***
Request to deliver only in 4.0 and not 3.3.
[ sizing = 2 weeks ]
[ sizing = 3 weeks ]
Updated with dependency on defect that tracks the 3.3 partial progress view work associated with this. The test execution monitor view parts of this enhancement is scheduled to be delivered in 4.0 instead of 3.3 (awaiting final approval, brought up at 4/25/2005 test project meeting) per request.
Requested move to 4.1 (consuming product and reporter agreed with this)
Deferring from 4.1 as per the official 4.1 enhancement plan. http://eclipse.org/tptp/home/project_info/featureplans/features.php?source=All&project=All&release=4.1&file=TPTPFeatures_4.1.xml
You may take a look at how activity feedback is presented in live/import agent scenarios in Profiling and Logging perspective. In the import Log and Profiling file case we get feedback in the Progress view and also in the status bar, in the live connection cases we get only the status bar info (there is no job created for profile and attach scenarios). The status bar feedback is sensitive to the selected agent in the (Profile or Log) Navigator (this cannot be done in Progress view), which allows to see how much data and how many events have been processed on a specific agent (which is currently collecting data).
There was a lightweight solution implemented in TPTP 4.1 that does not yet use a new view ("Test Execution Monitor") but might suffice for TPTP 4.2. I would suggest that greater support be pushed past TPTP 4.2 (just my opinion).
Based on feedback from reporter and other appropriate parties, this should be pushed from TPTP 4.2 into TPTP 4.3.
Correcting version for this enhancement (defaulting to the current release). See http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html for more information.
Correction: Future is a valid version for this enhancement based on http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html. As such, the implicit assumption is that is enhancement is of a lower priority. If incorrect, the originator should correct the version.
Updating target to future as requested by the PMC. Enhancements are targeted to future if not in plan for the current release.
Correcting priority since not a 4.5 candidate enhancement (see http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html).
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 the 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.
