| Summary: | Datapools are not portable. | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Paul Slauenwhite <paulslau> |
| Component: | TPTP | Assignee: | Paul Slauenwhite <paulslau> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | P2 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | housecleaned462 | ||
| Bug Depends on: | 195846 | ||
| Bug Blocks: | |||
|
Description
Paul Slauenwhite
Joe, please provide a sizing. Included in 4.5 plan for the Test Tools project. Please provide a sizing for this defect before Monday, November 12, 2007. When the user creates a datapool, add the required JARs to the project's classpath. Deferring to I6. Deferring to I7 as discussed by PMC/AG (http://wiki.eclipse.org/TPTP-AG-20080331#Test_Project). Deferring to future as discussed by PMC/AG (http://wiki.eclipse.org/TPTP-AG-20080331#Test_Project). This defect is impacting a consuming product. We should consider it in the TPTP 4.5.3 plan. Consider adding the datapool to the project's classpath and using project-relative paths. The datapool API
(org.eclipse.hyades.execution.runtime.datapool.IDatapoolFactory) could be passed a project-relative path and load the datapool using the following code:
URL datapoolResource = ClassLoader.getSystemResource("<datapool project-relative path><file path separator><datapool name>.datapool");
File datapoolFile = new File(datapoolResource .toURI());
(In reply to comment #9) > Consider adding the datapool to the project's classpath and using > project-relative paths. The datapool API > (org.eclipse.hyades.execution.runtime.datapool.IDatapoolFactory) could be > passed a project-relative path and load the datapool using the following code: > > URL datapoolResource = ClassLoader.getSystemResource("<datapool > project-relative path><file path separator><datapool name>.datapool"); > > File datapoolFile = new File(datapoolResource .toURI()); When the datapool is associated with an artifact (see 195846) or included on the Eclipse project's classpath (requires the user to be manually completed), the datapool is deployed to the target machine. The datapool should be added to the classpath of the test execution Java process so it can be loaded from its project-relative path (see above). This requires the datapool API > (org.eclipse.hyades.execution.runtime.datapool.IDatapoolFactory) to handle absolute and relative paths. This defect requires new test cases and documentation with the details on how to configure 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. 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. |