Community
Participate
Working Groups
Support annotations and launching/controlling two or more recorders in the Generic Recorder Framework. This enhancement covers various Generic Recorder Framework improvements required by recorder implementations (e.g Generic Java API Recorder - see https://bugs.eclipse.org/bugs/show_bug.cgi?id=119688): 1. Support for launching and controlling two or more recorders (separate recording session) or recording agents (single recording session) in parallel. For example, launching and controlling multiple recorders at the same time or launching and controlling multiple recording agents that all record various components of a system on one or more target hosts at the same time. This will require changes to the recording console to handle controlling multiple recording session and recording agents within the same recording session. Also, a method to synchronize (order) recorded events is required. Synchronization may occur at record time (e.g. centralized ticket reservation system) or reliably correlated at post-record time. Preferably, both options would be implemented so the recorder may select the best possible option. Provide an extension point for user-defined annotations to a recording session. The extension point would provide: -UI widgets (e.g. button) in the recorder controller view for controlling the user-defined annotation. -Common representation of the user annotations and their data in the trace model. -User-defined implementations of the user-defined annotation invoked on the recorded host (local or remote) when the user invoked the UI widget in the recorder controller view. Provide implementations of the extension point for the following user-defined annotations: -Comment -Start timer (name) -Stop timer (name) -Start transaction (name) -End transaction (name) -Pause recording -Resume recording -Split test (name) -Sync point (name) -Extension point for vendor customizations The TPTP Trace model and its loaders must leverage an annotation capability (e.g. Trace model instance referencing sections of an external annotation file) to keep large annotation data from exceeding the in-memory model capacity. For more details, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=144950.
Please assign to me.
Reassign to Paul.
Added: Since a recorder or recording agent captures the activity of a Java application, if is often necessary to capture, persist and reference other types of meta-data describing the application being recorded or its run-time (e.g OS or JVM). This meta-data can then be used for problem determination during a recording session or used in conjunction with the recording file during test suite generation. Provide a set of APIs for recorders or recording agents to invoke for emitting log (e.g. Common Base Event) and statistical data during a recording. For log data, the TPTP Common Base Event producer implementation. For statistical data, provide an API for recorders or recording agents to invoke for emitting statistical recording events. The statistical recording events API provides a simple Java implementation of each supported statistical recording event. The log and statistical recording events are serialized to XML using the http://www.eclipse.org/tptp/platform/documents/resources/cbe101spec/commonbaseevent1_0_1.xsd - Common Base Event V1.0.1 specification and http://www.eclipse.org/tptp/platform/documents/resources/dtd_xsd/statistical.xsd - Statistical Data Schema and emitted to the launching workbench. The custom Generic Recording Framework EMF loaders will be extended to support the log and statistical recording events. For more details, see enhancement https://bugs.eclipse.org/bugs/show_bug.cgi?id=139747.
Adding requirements from 83781 which are related to this enhancement so they can be tracked together. There is a need for the Recording Control/Feedback view to be shared across all types of tests that leverage recording. The view must be extendible to support a wide range of recording feedback that may be specific to any type of test. The view should also have the ability to display as a small window so users can see the recording control on the screen without having to see the full Eclipse workbench. This facilitates recording of a system/application under test from another GUI/browser, etc. while still seeing the recorder control/feedback. This view should also be flexible enough to display instructions/help text that might lead the user on how to create a recording.
*** Bug 83781 has been marked as a duplicate of this bug. ***
(In reply to comment #4) Updated Description Document with David's comments.
Merging back with feature #145146 for consideration in the 4.4 planing cycle since this feature was originally an offshoot of feature #145146 when it could not be contained in 4.3. *** This bug has been marked as a duplicate of bug 145146 ***
Closing since originator of duplicate defect is the same.
