TestRunner does not respect Working Directory set in Debugging Properties

[kiron1]

Our test executable expects to be invoked in a specific working directory where further assets are located.

From inspecting the code of GoogleTestRunner it automatically uses the directory where the executable is located. Is it be possible to extend GoogleTestRunner to use the same path for running the test as configured in the Debugging properties of the project?

[markusl]

Hi kiron1.

Generally, test executables should be self-contained and should have no dependencies to outside system. Would it be possible to configure your build system to copy the required assets to same place it puts the executable?

Regards,
Markus

[kiron1]

Hi Markus,

Thanks for quick reply.

Unfortunately coping is not an option, since the assets are quite huge. Therefor we would like to avoid any coping. We tried to use symlinks, but this does not work in a cross platform why without requiring Administrator rights on Windows.

[sabarn01]

mklink doesn't require administrator privileges.

On Mon, Jan 19, 2015 at 5:53 AM, kiron1 notifications@github.com wrote:

Hi Markus,

Thanks for quick reply.

Unfortunately coping is not an option, since the assets are quite huge.
Therefor we would like to avoid any coping. We tried to use symlinks, but
this does not work in a cross platform why without requireing Administrator
rights on Windows.

—
Reply to this email directly or view it on GitHub
#7 (comment)
.

Adam Barnett

[kiron1]

Thank you sabarn01, previously the build script was using mklink /D (which requires Administrator privileges), changed it mklink /J (which does not require Administrator privileges).