Community
Participate
Working Groups
Open an execution history in its viewer. Locate an even that contains a link back to the element in the test that generated that event. Click on the link to open the test. At this point, the instace of the ITestSuite held by the ExecutionHistory Viewer and the Test Suite editor are different. Any changes to the testsuite go un-noticed by the execution history viewer. So in the case where there is a Viewer listening to selection events in the execution history viewer and uses the following API to get to the data in the testsuite from the execution history executionHistory.getTest().get... It returns stale data. The execution history viewer should listen to resource chagnes on the associated testsuite to reload the testsuite model if necessary.
There's a ResourceCache written by Joe to allow TPTP reuse EMF resources loaded in memory, which will garantee the same resource is referenced by everybody. However curretly this cache is not being taken advantage of. It requires changes in all places with resource loading which is risky to do now. Deferring from 4.2 release.
Sizing updated as provided by Bianaca.
Targeting to future since not containable in 4.4.
As discussed on this week's Test Project call (January 22, 2007), the Test Project will focus on existing P1 - P2/Blocker - Major and P1/Normal and test creation/automation defects (omitting defects dependant on outstanding features) in TPTP 4.4. All other Test Project defects have been targeted to future. If this defect has been targeted to future and you/originator feel it should be completed in 4.4, please provide the necessary reason as a reply to this comment or a post to the Test Project mailing list (tptp-test-tooling-dev@eclipse.org). We will collectively triage and assess our resources to determine a case-by-case decision.
Correction: The Test Project mailing list is tptp-testing-tools-dev@eclipse.org.
Reassigning to the Project Lead.
This defect is still reproducible in TPTP 4.5.0 (http://www.eclipse.org/tptp/home/downloads/?ver=4.5.0).
Reproducible by opening a test suite and its test log in their editors, changing the logical name of the test suite, and note the test log viewer does not reload the test suite. However, reopening the test log viewer displays the correct logical name of the test suite.
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.
Reopening since still relevant.
Deferring to TPTP 4.7.0.
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.
