I am currently trying to run MSTest.exe from NCOV but I believe that the question is usually MSTest The command line can be applied to run .exe.
If I have "/ nizolation" logic, then MSTest.exe expects to find and use app.config. Without this, the NCOOVER does not capture any coverage information. So far by my research, it seems to be the need / noise of the encover
Profiles in the application
C: \ Program Files (x86) \ Microsoft Visual Studio 9.0 \ Common7 \ IDE \ MSTest.exe
Work folder
C: \ Documents and Settings \ MyProfile \ My Documents \ Visual Studio 2008 \ Projects \ XYZ \ XYZ.CoreTest \ bin \ Debug
Application logic
/ noisolation / testcontainer: "C: \ Documents and Settings \ MyProfile \ My Documents \ Visual Studio 2008 \ Projects \ XYZ \ XYZ.CoreTest \ bin \ Debug \ XYZ.CoreTest.dll "
Update: I said" C: \ Program Files (x86) \ Microsoft Visual Studio 9.0 \ Common7 \ IDE \ MSTest.exe.Config "is my check while trying to read (not surprisingly).
Update 2: If possible, I do not want to edit MSTest.exe.Config. It's not just very portable.
In a comment from Craig Stunts
How to do this with MSTE < P>
-
In Solution Explorer, right-click the solution (no project).
-
Add new items, add new items
-
Select test run configuration
-
Now select test run configuration item and add it
-
In Solution Explorer, double click on test run configuration you just created
-
Click on Deployment Item
-
Add your config file as a deployed file (or deploy to the entire folder, which is appropriate)
< / Li>
It took me a while, but I am in a similar condition and it works for me.
Comments
Post a Comment