Bug with the remote upload operation

[Broadnick]

When I try to execute my TestCase remotely, I receive the following error message : "The report file or directory could not be created. Report template does not contains a *.rxlog view file".

The problem is that for unknown reason, only two files (include in my Report Template Folder) are copied in the "...Agent\Data\Uploads\" directory on the remote machine. The other files are missing (including the .rxlog). Please, look at the image in attachment.

NOTE : My files were all set to " Always" in the property "Copy to output directory".

How can I control the package who is transfered to the remote machine?

[krstcs]

Without more information it will be hard to know what is happening.

What version of Ranorex are you using?
What are your test suite settings?

Can you upload your solution? If not, you can send it to [email protected]. Or, you can make a new solution that demonstrates the issue without any of your companies info.

[Broadnick]

Remote agent is a new feature of the Ranorex version 6.0.0...

See our complete test solution in attachment. It sounds like custom report template files are not zipped and transfered on the remote machine when we start execution using a remote agent. If I reset my report template to default, then everything runs successfully.

[krstcs]

Yes, I know, but I execute my test remotely using Jenkins, and since you didn't specify I tried not to assume, so I asked.

That would be my guess as well. I had mine setup on a network share (the template was there and the suites all pointed to the share '\\<server>\<share>\<template>') but it did the same thing when I deployed to my VMs for tests.

[Broadnick]

If I turn off the custom report in the test suite properties (back to default report template), then the problem does not occur. It seems that Ranorex does not transfer custom report template files on remote machine.

[krstcs]

Ranorex Team, please move this to the Bug Reports forum.

Thanks!

[Support Team]

Hi Everyone,

The issue was reproducible on our test environment and I added it to our internal bug-tracking system. Currently, we do not know when this issue will be fixed. This depends on various factors. Nevertheless, all reported bugs and feature requests are documented in the release notes, with every new version release of Ranorex.

In the meantime, I would suggest using one of the following workarounds:

• Locate the custom template folder on a network share that is accessible from the remote machine, too
• Copy the custom template folder to each machine (development and runtime) and use the same file location, for example, C:\Templates\NewCustomTemplate1

Thank you for your understanding.

Sincerely,
Johannes