Community
Participate
Working Groups
Unexpected error occurs when using the suite parameter. In the output below, the first path listed for the test suite is correct, but the error message shows a different, incorrect path. Ant script appended after the output. Test started! Test 'C:\Projects\Project1\Script1.testsuite' executing org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1$DiagnosticWrappedException : org.eclipse.core.internal.resources.ResourceException: Resource /Project1/Projects/Project1/Script1.testsuite does not exist. <project name="TPTP Ant Tasks Test Script" default="test" xmlns:tptp="antlib:org.eclipse.hyades.automation.client.adapters.ant"> <property name="eclipse.home" value="C:\Program Files\IBM\Rational Functional Tester_7.0.0.20060612_1934"/> <description> This ant script tests the TPTP automation ant task client adapters and also can be used to test the underlying execution of TPTP automatable services via the TPTP automation server </description> <!-- Execute TPTP test suites --> <target name="test" description="Executes TPTP Test Suites using default TPTP Ant Tasks"> <!-- Execute a TPTP test suite using the test task and providing the workspace --> <tptp:test workspace="C:\Program Files\IBM\Rational Functional Tester_7.0.0.20060612_1934\workspace" project="Project1" suite="Script1.testsuite" synchronicity="synchronous"/> </target>
This may (or may not) be caused by the fact that the project is not located in the workspace directory (although it is loaded in the workspace.)
Need to investigate if this is a regression or if it is due to unsupported function.
(In reply to comment #2) > Need to investigate if this is a regression or if it is due to unsupported > function. Is this defect a must-fix for TPTP V4.2.0 or can it be deferred to V4.3.0/V4.2.1?
As the reporter of the defect, I confirm that this is not a must-fix for 4.2.
Workaround is to use an ant filelist containing only one test.
I believe I understand the reason for this issue. Will try to address early in 4.4.
I used the fileset workaround to get past the problem for testsuites, however a similar problem occurs when a deployment is specified as well. Is there a similar workaround for the deployment parameter? I tried using a launch configuration and that approach appears to be unusable as well. For what it's worth, I did *not* have my project files under the workspace folder hierarchy. However, in my attempts to get things working I created a new workspace and imported all off my projects into the new workspace to no avail.
Deferring to i3 to allow completion of UI changes for other defects in time for UI freeze.
I was not able to re-produce this defect in the release version of TPTP 4.2.2 or in TPTP 4.3.1 final. In TPTP 4.4, I am currently unable to run a testsuite through an ant script for a different reason. Filing a separate defect for that issue.
Validated in TPTP 4.4 with the following ant target: <target name="execute.suite"> <tptp:execution project="org.eclipse.tptp.test.testservices.tests" resultsrefid="tptp.test.results1" results="junit_results/Windows_IA32/" suite="junit/Test.Sun142_TestServices.testsuite"/> </target> Closing.
