Community
Participate
Working Groups
Support for additional recorders in the framework. A generic Record facility would be help simplify the user experience. Remove the protocol and recording techniques from the initial UI (i.e., record button, wizard name) and emphasize the recording and creation of a new test (e.g., "Record Performance Test"). A user can be prompted for different recording protocols, etc.
Adding Julien to the CC list as his Junit-based tools integration Document (Bug 74791) also addresses a generic recording facility.
Changing target milestone to 4.0 and the component to test.http
*** Bug 78410 has been marked as a duplicate of this bug. ***
[ sizing= 6 week] This is still on the list to request deferment to 4.1, since it request UI/PII.
Downstream products no longer require and have withdrawn request. We should review further to determine if needed in future release.
was not withdrawn, still planned for 4.1
No access to design document, so directed to add design here. Also, note that sizing in design document is incorrect. Redesign Wizard UI so it is usable for all recorders, while still providing the ability for an individual recorder to define its own UI entry points. In this generic UI, emphasize that it is the creation of a test ("Create new test from recording") Create new extension point schemas so all recorder information can be conveyed through a plugin.xml Create generic data processor that is equipped to handle any message from the recorder agent, custom messages defined by recorder. Test generator defined specific to a unique recorder. Recording output may a "recording" (which will be a trace model in the final state -- 75026) or a testsuite.
Changing to P1 as per the 4.1 official plan.
Changing version to 4.2 so this gets considered as part of 4.2 plan, in case it doesn't get delivered in 4.1 due to developer supporting doc shortfall.
[ sizing = 6 weeks ] All dev work is complete (reference 109930). The work remaining is user (although user doc should be provided for HTTP recorder in 4.1) and SDK documentation.
code delivered in internal packages. Will be made public, along with doc & test as of 4.2 For the doc & test work: [ sizing = 6 weeks ]
proposed to be plan for 4.2 (plan keyword added)
Target set to 4.2
Reassign to Mark. [sizing = 3 weeks ]
Added a new bugzilla 122949 to track the documentation of this feature. See http://eclipse.org/tptp/groups/Architecture/documents/features/hf_122949.html for new description doc.
This feature was actually almost completely implemented in 4.1. Only remaining work is update of the documentation, see bugzilla 122949. Resolving this defect in 4.1.
Closing
