-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to specify working directory #71
Comments
It certainly is. In fact, Jonas and I have discussed this very enhancement a couple of days ago... However, it will take some time, since providing a general option does not suffice here - we need to be able to specify different working dirs for every test executable of the solution. Can you in the meantime fall back to copying your config and data files to your build directory? You should be able to do this with VS or even with GTA's test setup batch file... |
Just to let you know: We decided to implement the whole settings enhancement step by step, and the first step allows to specify the working dir on solution level. Thus, if all test projects of your solution need the same working dir, this will already be possible with the next release. Therefore, I'm already closing this issue - if you need more fine-grained working dir configuration, watch issue #74 |
Awesome. Solution level setting is working for me and my setup. Thanks! |
Support word wrap for New Project Wizard
I'd like to be able to specify the working directory. My setup usually is writing and debugging via my test runner in Visual Studio. This has the working directory set to the solution directory. Various test configuration and test data files are loaded relative to this path. Running via the test adapter fails for me since the working directory is set as the output executable directory. For me that is e.g. $(SolutionDir)\x64\Debug where I have builds for x64, win32, debug and release. Would this be possible?
The text was updated successfully, but these errors were encountered: