Community
Participate
Working Groups
General properties containing file/directory paths in test artifacts are not portable. Similar to the portability issue with datapools (see 195683), general properties containing file/directory paths in test artifacts are not portable. For example, deployed test dependency files are added to the CLASSPATH general property of a test artifact. However, these paths must be absolute (see http://help.eclipse.org/help32/topic/org.eclipse.hyades.test.doc.user/ref/rdeploymentGroundRules.htm), which is not portable (e.g. common test assets between multiple developers/workstations). One possible solution is to use workspace-relative paths or Eclipse variables (e.g. ECLIPSE_HOME).
Jerome, please provide a sizing.
[From https://bugs.eclipse.org/bugs/show_bug.cgi?id=142484]: The purpose of this bugzilla is to improve the ability to run the same JUnit plug-in test on various workspaces. Currently, the only way to ensure that a JUnit plug-in test can be run on two different machines (with different OS, installation directories, languages, etc.) is to use the "default deployment" in the test launch configuration. This ensures that appropriate options will be chosen, depending on the machine specifics. If one creates a workbench location, this location will contain fixed values, such as directories, VM args, and so on. For each option that the workbench location editor provides, it should be possible to choose an "automatic" value. The involved options are: - workbench location - program arguments - VM arguments
*** Bug 142484 has been marked as a duplicate of this bug. ***
Required for the TPTP BVTs.
When test assets are added to an artifact, only the project-relative path should be added to the General Properties page of the Artifact editor. When the test is executed, the absolute paths to the dependent test assets are resolved and deployed. Requires new test cases to cover absolute and project-relative paths in the General Properties page of the Artifact. Also, requires new documentation outlining how paths can be entered in the General Properties page of the Artifact editor.
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.
