Community
Participate
Working Groups
Test execution harness ignores non-execution test execution events. The org.eclipse.hyades.execution.harness.XMLExecutionDataProcessor class that is responsible for processing and loading test execution events ignores non-execution test execution events. For example, any event other than: <EXECUTION>...</EXECUTION> Often, test authors want to emit log (e.g. Common Base Event), statistical, trace and/or arbitrary XML fragments from their JUnit test class back to the launching workbench. The underlying loaders handle mixed events (e.g. consuming, parsing and loading in context) but this function is disabled during test execution since the XMLExecutionDataProcessor class registers a org.eclipse.hyades.loaders.hierarchy.IgnoredXMLFragmentLoader instance with the parent XML loader and filters delegates all non-execution test execution events to the IgnoredXMLFragmentLoader for loading (see XMLExecutionDataProcessor #isIgnoredElement()). Please consider this a P1 priority since it is required for features schedule for release as a TPTP V4.2.0 Technology Preview.
Per meeting with Paul Slauenwhite, Marius Slavescu, Joe Toomey, Ashish Mathur, Ernest Jessee, and myself on May 11th, it was decided by consensus that it was too risky this late in 4.2 to try to address this defect properly, and it raises several related design issues, some affecting user experience. All agreed that this needs to be addressed, and agreed that 4.3 was the appropriate release vehicle.
Joe, we had earlier tabled this to 4.3, and should now revisit and decide what we are going to do and when.
Based on priority and available resources, this defect is considered for deferral from 4.3. If you object to this deferral, please provide a comment ASAP explaining the reason that you need this in 4.3 and we will take that into consideration.
Re-targeting all non-blocking/critical defects to 4.4 as decided in yesterday's AG call.
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.
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.
