Bugzilla – Full Text Bug Listing
| Summary: | [Functionality] XMLExecutionDataProcessor does not support model loading to existing resource | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Joe Toomey <jptoomey> |
| Component: | TPTP | Assignee: | Joe Toomey <jptoomey> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | paulslau |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | closed471 | ||
|
Description
Joe Toomey
Requirement for fix no longer critical for consumer [ sizing = 3 days ] Paul has some interest in this, as he was just discussing the requirement to add pause/resume support to the TPTP manual runner today. I'm pretty sure he won't get to this in 4.1 either, but I'm adding him to the cc list so he knows which defect to look for in the future. Moving back to TPTP 4.1 i2 in case Paul needs it for manual tests. Paul please let me know if you will require this in 4.1 i2 (if not I will push to future). Hi Scott, Unfortunately, due to a resource deficiency for feature #74841, we will not be adding pause/resume functionality in the new manual test client in v4.1 (i2). However, this function will be added early in v4.2 so completing this defect in v4.1 (i2) would mean we could start this work item early in v4.2 (i1). If resources are not available, completing this defect in v4.2 (i1) would suffice. Just curios, Paul why do you need XMLExecutionDataProcessor in the manual test client (I assume that the manual test client doesn't use the test EMF model)? All TPTP tests are run through the test execution harness and produce execution history models, so they all implicitly use XMLExecutionDataProcessor. We are providing function to for the manual test client to consume the EMF model. ASAIK the current manual test client (/org.eclipse.hyades.test.tools.core/src-manual-runner) doesn't require EMF test model or harnes code, that's why I was curios why the new one would add dependency on those components (which I think should not be required). I will comment more on the Bug 74841. Regardin Pause/Stop I don't think the manual test client should generate execution results, it just needs to send/save the raw events (as all the other runners do). The manual test runner works the same way the other runners do in the test space today -- it streams back events as they happen, and those events are model loaded at the time they arrive at the workbench. They are not stored once they are model loaded. We have no way of knowing if the user will gesture to pause at some point in time. When they do gesture to pause, the prior XML fragements are gone -- they were already loaded and discarded. As for depenedency, the test runners all have runtime access to EMF and the test model as confiured in the RAC plugin today. This is used for datapool runtime access, among other things. Given the enhancements that are being proposed for the manual runner (like embedding files in the model and displaying them in the runner), and given that EMF and the test model are already available on the runtime side, I don't see a good reason to continue making a transform to XML and supporting two different XML representations of a test behavior. But we can discuss this at Paul's next meeting on the manual runner enhancements. (Paul, can you invite Maruis to these meetings?) Thanks Joe for the explanation. Paul please invite me to those meeting. I agree with the testcase model, I believe the facade would be used instead of the EMF generated classes, same for datapools. 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. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html). 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. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html). 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. |