Community
Participate
Working Groups
Test Harness should be able to invoke user selectable agent data collectors when test is invoked on specified machines and associate the collected data results as with the test run. These choices, including which data should be collected, needs to be persisted (with some naming scheme), so that subsequent test runs can re-use the same data collection choices (or easily edit them). The initial requirement is to invoke agent data collectors which are independent of the test details itself (such as perfmon or other performance monitoring data collectors).
In addition, we need to enable concurrent test execution and profiling. This may require collabortation with the toronto profiling folks to expose some of their code in a reusable fashion (so it can be consuemd by the test execution harness.)
This enhancement request has been split into a new enhancement request to address "concurrent test execution and profiling" with this request only covering "data collectors being associated to a test, run with a test and then the data integrated with the test results". Joe Toomey's comment on 2004-10- 14 16:32 (additional comment #1 below) has migrated to another enhancement request (likely be addressed in a later release such as 3.3).
I'm attempting to get this feature re-targeted from 3.2i2 to 3.3. This enhancement request is being deferred after discussion at 11/30/2004's weekly execution meeting. There are two dependencies that were uncovered late in the iteration that made implementation of this feature very difficult to complete in 3.2 i2. Current UI extensibility for launch configurations (added value such as having the ability to contribute additional configuration tabs for particular agent types (that were specific to each agent) is not easily possible without writing this code ourselves and also backend support for the discovery of installed agents and the overall facility for the general interaction and control is missing from the current agent controller implementation. This should have been uncovered in the design phase but was not uncovered until the UI review and subsequent research while implementing certain parts of the code.
Downstream products no longer require and have withdrawn request. We should review further to determine if needed in future release.
Changing to P1 as per the 4.1 official plan.
Pushed to a future release due to lack of resources in this release.
Changed Version from 4.1 to 4.2 for inclusion in TPTP 4.2 planning, given that this was scoped out of 4.1.
proposed to be plan for 4.2 (plan keyword added)
Target set to 4.2
This enhancement request will be split into two entries for tracking purposes.
This defect is dependent on the new agent controller to be implemented the initially designed way -- there might be a lighter-weight solution that is specific to certain cases that will still meet the consumer's requirements. Clarification on the new agent controller and its roll out to consumers in TPTP 4.2 needs to be obtained. Without the new agent controller features that this item depends on a scaled down solution will have to be implemented.
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).
This feature also requires that when a test is executed in profiling or debug mode, the associated perspective is opened. For example, for debugging: //Attempt to open the Debug Perspective: IWorkbench workbench = PlatformUI.getWorkbench(); IWorkbenchWindow activeWorkbenchWindow = workbench.getActiveWorkbenchWindow(); if (!activeWorkbenchWindow.getActivePage().getPerspective().getId().equals("org.eclipse.debug.ui.DebugPerspective")) { //$NON-NLS-1$ workbench.showPerspective("org.eclipse.debug.ui.DebugPerspective", activeWorkbenchWindow); //$NON-NLS-1$ } This should be done in org.eclipse.hyades.execution.harness.TestExecutionHarnessExecutorStub.debugAndLaunch(IProgressMonitor) but since this TestExecutionHarnessExecutorStub is not aware of the workbench (or the UI), we need to create a lower-level TestExecutionHarnessExecutorStub in a test UI plug-in for opening the associated perspective when launching from the Eclipse workbench.
Work-around: https://bugs.eclipse.org/bugs/show_bug.cgi?id=138736#c27 Work-around Patch: https://bugs.eclipse.org/bugs/show_bug.cgi?id=138736#c28
Changing to a defect since this is function that should have been implemented with the org.eclipse.hyades.test.core.launchconfigLaunchableType extension point.
*** Bug 174218 has been marked as a duplicate of this bug. ***
In addition: [Defect #174218]: Launching a JUnit/Plug-in test in debug mode opens the Test perspective. When running a debug launch configuration for a TPTP JUnit or TPTP JUnit Plug-in test suite, the Test perspective is opened instead of the Debug perspective.
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. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
Closing.
Mistakenly closed for the originator. Reopening for the originator to verify/close.
Re-resolving as WONTIFX.
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.
