Relative Paths for Visual Studio Generic Tests

To make generic tests robust enough to run for all developers on your team and on the build server, you are likely going to want to avoid hard coding the path to the executable.  To do this successfully, you need to have a list of all the environment variables that are available when the test executes.  These can be obtained by creating a generic test with the existing program as %COMSPEC% (the fully pathed location for cmd.exe) and setting “/C set” as the Commnd-line arguments.  The result, with all standard environment variables pulled out, is as follows:

Where I have substituted the following values:

Of these, the most important in my experience is %TestLocation% as this identifies the directory of the test project, and therefore, you can find relative directories from that.  For example, if you want to find a file located in the nuget packages directory you would use

Leave a Reply


Contact Us
Email: info@IntelliTect.com
Phone: (509) 315-3400




Testimonials

“Mark recognizes that the Business is a key stake holder in the entire .NET conversion. He has helped to create a cooperative environment between the Business and Intellitect as we’ve partnered to make this a successful project.  Mark has a top-notch team that has supported both the technical and Business needs.”
- Shana, Liz and Tanya, Avista Utilities, Spokane, WA
CONTACT US: (509) 315-3400 | Info@IntelliTect.com | Jobs | Site Map