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:
<SolutionDirectory>:The hard coded path tothe full solution directory
<TestRunDirectory>:The unique MSTest generated directory foreachtest run
<UUIDX>:Aunique id value.
<ProjectDirectory>:The directory of the project that contains the generic test.
<ComputerName>:The name of the computer executing the tests.
<LocalAppData>:The users local app data directory.
<UserProfile>:The directory of the users local profile.
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