Skip to main content



      Home
Home » Archived » Test and Performance Tools Platform (TPTP) » TPTP automation errors
TPTP automation errors [message #90751] Tue, 02 January 2007 14:53 Go to next message
Eclipse UserFriend
I'm trying to automate my TPTP environment using the supplied Ant tasks and
I have yet to get anything beyond the most trivial of examples working. I
am interested to know if anyone has been able to accomplish a decent level
of automation and I'm all ears and would greatly appreciate any pointers
anyone may have.

Here is my basic scenario:

Parameters:
tptp.automation.eclipse=C:/Development/Tools/eclipse
tptp.test.workspace=C:/Development/Projects/Workspace
tptp.test.project=Test

Ant target:
<target name="run_tests">
<tptp:test deployment="resources/TPTP/deployments/Solaris.deploy">
<fileset dir="C:/Development/Projects/Workspace/Test"
includes="**/TestManager.testsuite"/>
</tptp:test>
</target>

All resources exist in the specified location(s). I can run my tests
successfully from the IDE.

I get the following error using this configuration:
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1$Diagno sticWrappedException:
org.eclipse.core.internal.resources.ResourceException: Resource
/Test/Development/Projects/Workspace/Test/resources/TPTP/dep loyments/Solaris.deploy
does not exist.
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.handleDe mandLoadException(ResourceSetImpl.java:307)

It looks like the project name is prepended to the path to the deployment
I'm trying to utilize but I don't know why.

Using a full path to the deployment resource does not work, either.

For what it's worth, I get the same type of ResourceException should I try
to use the default deployment but explicitly specify the test suite I want
to run. The only manner in which I have been able to get out of the
starting blocks is to use a fileset to discover the test suite resource(s).

To try to work around the issue(s) I saved the launch configuration and
tried that approach but ran into another wall. Below is the ant target and
subsequent exception from that effort.

<target name="run_tests">
<tptp:test
configuration=" C:\Development\Projects\Workspace\Test\resources\TPTP\Proces sManagerTests.launch "/>
</target>

java.lang.NullPointerException
at
org.eclipse.hyades.test.core.services.AbstractTestExecutionS ervice.initialize(AbstractTestExecutionService.java:556)


This error is the same error I get when I don't specify a test suite. Why
should I need to specify a test suite when I'm specifying a configuration?
Doesn't a launch configuration contain everything it needs? Internally, the
..launch file has a .testsuite file mapped to key so that seems redundant to
me. If I do specify a test suite as an attribute to the tptp:test task, I
run into the same problem I was having with the .deploy resource -- the item
cannot be found.


Another issue is that tptp.test.project is documented as being optional but
I have yet to have found a configuration combination that allows for the
omission of this parameter from either the environment or as an attribute in
the tptp:test task.

java.lang.NullPointerException
at
org.eclipse.hyades.automation.server.AbstractProjectSensitiv eService.refreshProject(AbstractProjectSensitiveService.java :99)


Any suggestions are welcome.

Thanks,
Jonathan
Re: TPTP automation errors [message #90998 is a reply to message #90751] Sun, 07 January 2007 09:54 Go to previous messageGo to next message
Eclipse UserFriend
Two bugs reports / discussions are worth looking, I believe :

https://bugs.eclipse.org/bugs/show_bug.cgi?id=163387

https://bugs.eclipse.org/bugs/show_bug.cgi?id=146539


"Jonathan Brown" <jonathan_w_brown@hotmail.com> wrote in message
news:ened8k$734$1@utils.eclipse.org...
> I'm trying to automate my TPTP environment using the supplied Ant tasks
> and I have yet to get anything beyond the most trivial of examples
> working. I am interested to know if anyone has been able to accomplish a
> decent level of automation and I'm all ears and would greatly appreciate
> any pointers anyone may have.
>
> Here is my basic scenario:
>
> Parameters:
> tptp.automation.eclipse=C:/Development/Tools/eclipse
> tptp.test.workspace=C:/Development/Projects/Workspace
> tptp.test.project=Test
>
> Ant target:
> <target name="run_tests">
> <tptp:test deployment="resources/TPTP/deployments/Solaris.deploy">
> <fileset dir="C:/Development/Projects/Workspace/Test"
> includes="**/TestManager.testsuite"/>
> </tptp:test>
> </target>
>
> All resources exist in the specified location(s). I can run my tests
> successfully from the IDE.
>
> I get the following error using this configuration:
> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1$Diagno sticWrappedException:
> org.eclipse.core.internal.resources.ResourceException: Resource
> /Test/Development/Projects/Workspace/Test/resources/TPTP/dep loyments/Solaris.deploy
> does not exist.
> at
> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.handleDe mandLoadException(ResourceSetImpl.java:307)
>
> It looks like the project name is prepended to the path to the deployment
> I'm trying to utilize but I don't know why.
>
> Using a full path to the deployment resource does not work, either.
>
> For what it's worth, I get the same type of ResourceException should I try
> to use the default deployment but explicitly specify the test suite I want
> to run. The only manner in which I have been able to get out of the
> starting blocks is to use a fileset to discover the test suite
> resource(s).
>
> To try to work around the issue(s) I saved the launch configuration and
> tried that approach but ran into another wall. Below is the ant target
> and subsequent exception from that effort.
>
> <target name="run_tests">
> <tptp:test
> configuration=" C:\Development\Projects\Workspace\Test\resources\TPTP\Proces sManagerTests.launch "/>
> </target>
>
> java.lang.NullPointerException
> at
> org.eclipse.hyades.test.core.services.AbstractTestExecutionS ervice.initialize(AbstractTestExecutionService.java:556)
>
>
> This error is the same error I get when I don't specify a test suite. Why
> should I need to specify a test suite when I'm specifying a configuration?
> Doesn't a launch configuration contain everything it needs? Internally,
> the .launch file has a .testsuite file mapped to key so that seems
> redundant to me. If I do specify a test suite as an attribute to the
> tptp:test task, I run into the same problem I was having with the .deploy
> resource -- the item cannot be found.
>
>
> Another issue is that tptp.test.project is documented as being optional
> but I have yet to have found a configuration combination that allows for
> the omission of this parameter from either the environment or as an
> attribute in the tptp:test task.
>
> java.lang.NullPointerException
> at
> org.eclipse.hyades.automation.server.AbstractProjectSensitiv eService.refreshProject(AbstractProjectSensitiveService.java :99)
>
>
> Any suggestions are welcome.
>
> Thanks,
> Jonathan
>
>
>
>
>
Re: TPTP automation errors [message #91014 is a reply to message #90998] Tue, 09 January 2007 09:35 Go to previous messageGo to next message
Eclipse UserFriend
The first one doesn't seem pertinent to me but the second bug you pointed
out could be related.

Also, I came across this bug report that is definitely the same issue:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=146901

I think the same underlying flaw is also impacting the deployment parameter.





"Ravi Roy" <ravi.aroy@gmail.com> wrote in message
news:enr1i5$nf8$1@utils.eclipse.org...
> Two bugs reports / discussions are worth looking, I believe :
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=163387
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=146539
>
>
> "Jonathan Brown" <jonathan_w_brown@hotmail.com> wrote in message
> news:ened8k$734$1@utils.eclipse.org...
>> I'm trying to automate my TPTP environment using the supplied Ant tasks
>> and I have yet to get anything beyond the most trivial of examples
>> working. I am interested to know if anyone has been able to accomplish a
>> decent level of automation and I'm all ears and would greatly appreciate
>> any pointers anyone may have.
>>
>> Here is my basic scenario:
>>
>> Parameters:
>> tptp.automation.eclipse=C:/Development/Tools/eclipse
>> tptp.test.workspace=C:/Development/Projects/Workspace
>> tptp.test.project=Test
>>
>> Ant target:
>> <target name="run_tests">
>> <tptp:test deployment="resources/TPTP/deployments/Solaris.deploy">
>> <fileset dir="C:/Development/Projects/Workspace/Test"
>> includes="**/TestManager.testsuite"/>
>> </tptp:test>
>> </target>
>>
>> All resources exist in the specified location(s). I can run my tests
>> successfully from the IDE.
>>
>> I get the following error using this configuration:
>> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1$Diagno sticWrappedException:
>> org.eclipse.core.internal.resources.ResourceException: Resource
>> /Test/Development/Projects/Workspace/Test/resources/TPTP/dep loyments/Solaris.deploy
>> does not exist.
>> at
>> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.handleDe mandLoadException(ResourceSetImpl.java:307)
>>
>> It looks like the project name is prepended to the path to the deployment
>> I'm trying to utilize but I don't know why.
>>
>> Using a full path to the deployment resource does not work, either.
>>
>> For what it's worth, I get the same type of ResourceException should I
>> try to use the default deployment but explicitly specify the test suite I
>> want to run. The only manner in which I have been able to get out of the
>> starting blocks is to use a fileset to discover the test suite
>> resource(s).
>>
>> To try to work around the issue(s) I saved the launch configuration and
>> tried that approach but ran into another wall. Below is the ant target
>> and subsequent exception from that effort.
>>
>> <target name="run_tests">
>> <tptp:test
>> configuration=" C:\Development\Projects\Workspace\Test\resources\TPTP\Proces sManagerTests.launch "/>
>> </target>
>>
>> java.lang.NullPointerException
>> at
>> org.eclipse.hyades.test.core.services.AbstractTestExecutionS ervice.initialize(AbstractTestExecutionService.java:556)
>>
>>
>> This error is the same error I get when I don't specify a test suite.
>> Why should I need to specify a test suite when I'm specifying a
>> configuration? Doesn't a launch configuration contain everything it
>> needs? Internally, the .launch file has a .testsuite file mapped to key
>> so that seems redundant to me. If I do specify a test suite as an
>> attribute to the tptp:test task, I run into the same problem I was having
>> with the .deploy resource -- the item cannot be found.
>>
>>
>> Another issue is that tptp.test.project is documented as being optional
>> but I have yet to have found a configuration combination that allows for
>> the omission of this parameter from either the environment or as an
>> attribute in the tptp:test task.
>>
>> java.lang.NullPointerException
>> at
>> org.eclipse.hyades.automation.server.AbstractProjectSensitiv eService.refreshProject(AbstractProjectSensitiveService.java :99)
>>
>>
>> Any suggestions are welcome.
>>
>> Thanks,
>> Jonathan
>>
>>
>>
>>
>>
>
>
Re: TPTP automation errors [message #103859 is a reply to message #91014] Mon, 09 July 2007 13:04 Go to previous message
Eclipse UserFriend
Hi Johnathon and Ravi,
Joe Tommey from the Test Project has said that these issues have been
fixed in 4.4 with the exception of this one:
> >> To try to work around the issue(s) I saved the launch configuration and

> >> tried that approach but ran into another wall. Below is the ant target

> >> and subsequent exception from that effort.

> >>

> >> <target name="run_tests">

> >> <tptp:test

> >> configuration=" C:\Development\Projects\Workspace\Test\resources\TPTP\Proces sManagerTests.launch "/>

> >> </target>

> >>

> >> java.lang.NullPointerException

> >> at

> >> org.eclipse.hyades.test.core.services.AbstractTestExecutionS ervice.initialize(AbstractTestExecutionService.java:556)

> >>

> >>

> >> This error is the same error I get when I don't specify a test suite.

> >> Why should I need to specify a test suite when I'm specifying a

> >> configuration? Doesn't a launch configuration contain everything it

> >> needs? Internally, the .launch file has a .testsuite file mapped to key

> >> so that seems redundant to me. If I do specify a test suite as an

> >> attribute to the tptp:test task, I run into the same problem I was
> >> having

> >> with the .deploy resource -- the item cannot be found.

This issue is covered by the following 4.4.1 defect (a patch file is already
attached.) https://bugs.eclipse.org/bugs/show_bug.cgi?id=194212.

You can move up to the latest TPTP release here:

http://www.eclipse.org/tptp/home/downloads/?ver=4.4.0


Paul
"Jonathan Brown" <jonathan_w_brown@hotmail.com> wrote in message
news:eo097l$9ar$1@utils.eclipse.org...
> The first one doesn't seem pertinent to me but the second bug you pointed
> out could be related.
>
> Also, I came across this bug report that is definitely the same issue:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=146901
>
> I think the same underlying flaw is also impacting the deployment
> parameter.
>
>
>
>
>
> "Ravi Roy" <ravi.aroy@gmail.com> wrote in message
> news:enr1i5$nf8$1@utils.eclipse.org...
>> Two bugs reports / discussions are worth looking, I believe :
>>
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=163387
>>
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=146539
>>
>>
>> "Jonathan Brown" <jonathan_w_brown@hotmail.com> wrote in message
>> news:ened8k$734$1@utils.eclipse.org...
>>> I'm trying to automate my TPTP environment using the supplied Ant tasks
>>> and I have yet to get anything beyond the most trivial of examples
>>> working. I am interested to know if anyone has been able to accomplish
>>> a decent level of automation and I'm all ears and would greatly
>>> appreciate any pointers anyone may have.
>>>
>>> Here is my basic scenario:
>>>
>>> Parameters:
>>> tptp.automation.eclipse=C:/Development/Tools/eclipse
>>> tptp.test.workspace=C:/Development/Projects/Workspace
>>> tptp.test.project=Test
>>>
>>> Ant target:
>>> <target name="run_tests">
>>> <tptp:test deployment="resources/TPTP/deployments/Solaris.deploy">
>>> <fileset dir="C:/Development/Projects/Workspace/Test"
>>> includes="**/TestManager.testsuite"/>
>>> </tptp:test>
>>> </target>
>>>
>>> All resources exist in the specified location(s). I can run my tests
>>> successfully from the IDE.
>>>
>>> I get the following error using this configuration:
>>> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1$Diagno sticWrappedException:
>>> org.eclipse.core.internal.resources.ResourceException: Resource
>>> /Test/Development/Projects/Workspace/Test/resources/TPTP/dep loyments/Solaris.deploy
>>> does not exist.
>>> at
>>> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.handleDe mandLoadException(ResourceSetImpl.java:307)
>>>
>>> It looks like the project name is prepended to the path to the
>>> deployment I'm trying to utilize but I don't know why.
>>>
>>> Using a full path to the deployment resource does not work, either.
>>>
>>> For what it's worth, I get the same type of ResourceException should I
>>> try to use the default deployment but explicitly specify the test suite
>>> I want to run. The only manner in which I have been able to get out of
>>> the starting blocks is to use a fileset to discover the test suite
>>> resource(s).
>>>
>>> To try to work around the issue(s) I saved the launch configuration and
>>> tried that approach but ran into another wall. Below is the ant target
>>> and subsequent exception from that effort.
>>>
>>> <target name="run_tests">
>>> <tptp:test
>>> configuration=" C:\Development\Projects\Workspace\Test\resources\TPTP\Proces sManagerTests.launch "/>
>>> </target>
>>>
>>> java.lang.NullPointerException
>>> at
>>> org.eclipse.hyades.test.core.services.AbstractTestExecutionS ervice.initialize(AbstractTestExecutionService.java:556)
>>>
>>>
>>> This error is the same error I get when I don't specify a test suite.
>>> Why should I need to specify a test suite when I'm specifying a
>>> configuration? Doesn't a launch configuration contain everything it
>>> needs? Internally, the .launch file has a .testsuite file mapped to key
>>> so that seems redundant to me. If I do specify a test suite as an
>>> attribute to the tptp:test task, I run into the same problem I was
>>> having with the .deploy resource -- the item cannot be found.
>>>
>>>
>>> Another issue is that tptp.test.project is documented as being optional
>>> but I have yet to have found a configuration combination that allows for
>>> the omission of this parameter from either the environment or as an
>>> attribute in the tptp:test task.
>>>
>>> java.lang.NullPointerException
>>> at
>>> org.eclipse.hyades.automation.server.AbstractProjectSensitiv eService.refreshProject(AbstractProjectSensitiveService.java :99)
>>>
>>>
>>> Any suggestions are welcome.
>>>
>>> Thanks,
>>> Jonathan
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
Previous Topic:TPTP Behavior model and BVRExecutionOccurrence
Next Topic:[AGR] Compatibility between AGR 4.3 and AGR 4.4
Goto Forum:
  


Current Time: Mon Jul 21 21:52:19 EDT 2025

Powered by FUDForum. Page generated in 0.05826 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top