| Summary: | Manual and URL Tests should use the Test launch configuration | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Dominique Guilbaud <dguilbaud> |
| Component: | TPTP | Assignee: | Julien Canches <julien.canches> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | julien.canches |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | 74841 | ||
| Bug Blocks: | |||
|
Description
Dominique Guilbaud
This wasn't done without reason. There is a nasty hack that is done in the ManualTestLuanchConfigurationDelegate, and without this hack, manual test execution will not work. The line is: testSuite.getImplementor().setResource(createTestScript(testSuite)); The createTestScript call does a transform on the test behavior in the test suite, converting it to the XML format understood by the manual test runner. It then puts that transformed XML into the resource property of the test behavior before the execution harness is called. (The fact that the XML is put in the resource property is the big hack.) This was all done because the manual test runner is actually an old WSAD component written in swing, and knows nothing about the test model. There is a different enhancement for 4.0 that tracks replacing the manual runner (added a dependency for this), and that replacement runner should interpret the test model directly instead of requiring the transformed model. At that point, we could use the default hyades test launch configuration. Thanks Julien -- if you can make the change you described to the generic launch delegate, we could remove the need for the manual launch config type, which would be good. During the Test User Experience meeting, it was agreed that the same principle should apply to URL test. Changing this bugzilla Summary to reflect this decision. A status on this, julien? Sorry for the delay: this defect was fixed in i2. *** Bug 83845 has been marked as a duplicate of this bug. *** ACTION: Please verify/close this defect. Verified on TPTP-4.3.0-200611070100 driver. |