Ranorex version: 7.0.0
System: local VM and remote VM running Windows Server 2012r2
Source control and CI: VSO 2013, MTM 2013,
Im having an issue where a set of e2e tests are failing at a specific point, it doesn't appear to be a problem with the AUT as it works fine manually but I get the attached error which ive never seen before suggesting missing dlls or dependancies
I am only getting this error when running the test through our MTM test agent, so it runs ok locally just not overnight and when manually on the automation sandbox which makes sense as QTAgent32 is the application that runs the tests overnight
any help would be greatly appreciated
e2e test failing due to missing dll's or dependencies
-
- Posts: 22
- Joined: Thu Dec 03, 2015 11:58 am
e2e test failing due to missing dll's or dependencies
You do not have the required permissions to view the files attached to this post.
Re: e2e test failing due to missing dll's or dependencies
Hi Andrew,
It seems that the Neotys package did not get deployed to the MTM machine.
Please make sure that all dependencies and the whole "package" folder gets deployed to the MTM machine.
Best regards,
asdf
It seems that the Neotys package did not get deployed to the MTM machine.
Please make sure that all dependencies and the whole "package" folder gets deployed to the MTM machine.
Best regards,
asdf
-
- Posts: 22
- Joined: Thu Dec 03, 2015 11:58 am
Re: e2e test failing due to missing dll's or dependencies
Hi,
How do I check that it has been deployed? I have checked in the appropriate folder but only shows the .exe for each test suite and a shared dll as shown below
Alternatively how can I purge neoload form Ranorex as it is not required as part of the test suite
Thanks
How do I check that it has been deployed? I have checked in the appropriate folder but only shows the .exe for each test suite and a shared dll as shown below
Alternatively how can I purge neoload form Ranorex as it is not required as part of the test suite
Thanks
You do not have the required permissions to view the files attached to this post.
-
- Posts: 22
- Joined: Thu Dec 03, 2015 11:58 am
Re: e2e test failing due to missing dll's or dependencies
I have removed the neoload references from my project that seems to remove all the errors but one of them, does anyone know where the below reference originates from?
Thanks
Thanks
You do not have the required permissions to view the files attached to this post.
Re: e2e test failing due to missing dll's or dependencies
Hi,
Have you checked if the module EnterHHBusinessUse is available on the target system?
Have you checked if the module EnterHHBusinessUse is available on the target system?
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
-
- Posts: 22
- Joined: Thu Dec 03, 2015 11:58 am
Re: e2e test failing due to missing dll's or dependencies
I can see the module on the target machine if I load the deployed project using test suite runner but when running the test there get a very similar error
You do not have the required permissions to view the files attached to this post.
Re: e2e test failing due to missing dll's or dependencies
Hi Andrew,
I would suggest, having a look at this UserGuide article. There is a detailed description on how to deploy your Ranorex tests to another environment.
If you are still facing this problem, I would suggest contacting Ranorex Support directly. ([email protected])
Best regards,
asdf
I would suggest, having a look at this UserGuide article. There is a detailed description on how to deploy your Ranorex tests to another environment.
If you are still facing this problem, I would suggest contacting Ranorex Support directly. ([email protected])
Best regards,
asdf
-
- Posts: 22
- Joined: Thu Dec 03, 2015 11:58 am
Re: e2e test failing due to missing dll's or dependencies
Purging the neoload modules did actually resolve this, the second issue was the project was not updating correctly in visual studio so the fix was not showing in the overnight run