Community
Participate
Working Groups
When execution event provides information about the test script file and line number of the invocation, log viewer should provide the function to navigate back to the code.
This will require a little model extension to include the test script data.
Updating Version from 4.1 to 4.2 and Priority to P1 for inclusion as TPTP 4.2 request.
Reassigning to Bianca per her request.
proposed to be plan for 4.2 (plan keyword added)
Target set to 4.2
Available in build TPTP-4.2.0-200601230100 or later. Implemented as a sample extension to "org.eclipse.hyades.test.ui.executionHistoryExtension.actionExtension" (refer to bug 103555). See class org.eclipse.hyades.test.ui.forms.actions.OpenJavaScriptAction and its javadoc for details. By default this extension is NOT registered. Vendor interested in using it need to have 2 things: 1) generated test log (a.k.a. execution history) file should contain java script class information as ExecutionEvent properties. 2) an extension to "org.eclipse.hyades.test.ui.executionHistoryExtension.actionExtension" extension point need to be registered either using the action class OpenJavaScriptAction as is or implementing your own. The registered action will show up as a push button in Test Log Viewer, next to the Events tree and listen to selection changes on the Events tree. When the right event (with properties for java script file information) is selected, this action will become enabled. When clicked, it will open up the java script in eclipse JDT java editor and highlight the line number provided in the event proeprties. Note: since this sample action uses JDT java editor, JDT has to present in the eclipse shell. It does not work in RCP.
ACTION: Please verify/close this defect.
Closing by default since not closed by the originator in the 7+ months since being resolved. Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct.
Correcting component.