I'm running into a situation where I need to enable the profiler however I do NOT have the ability to just open visual studio and click on a profiler choice, as I'm trying to get things to build on a headless build slave which runs as "nt authority\system."
This slave also had some churn on it in terms of having to reinstall visual studio 2015 enterprise (after installing JustMock)?
Currently I'm running Visual Studio 2015 update 3
Just Mock is version 2015.2.715.1
I also have a diagnostic script to see if the various environment variables are properly set based off some other searches:
write-host "COR_ENABLE_PROFILING: $($env:COR_ENABLE_PROFILING)"
write-host "JUSTMOCK_INSTANCE: $($env:JUSTMOCK_INSTANCE)"
write-host "COR_PROFILER: $($env:COR_PROFILER)"
whoami
When I run this on my build slave it presents me with:
COR_ENABLE_PROFILING: 1
JUSTMOCK_INSTANCE: 1
COR_PROFILER: {B7ABE522-A68F-44F2-925B-81E7488E9EC0}
nt authority\system
1 Answer, 1 is accepted
If I understand you correctly your scenario is to execute JustMock tests from a build script or command line? If this is the case, you are on the right path. But please have in mind that those environment variables should be set to the process that will execute the tests.
With other words, if you are doing this from build script apply the environment variables before executing the tests. I will also recommend you to check this Windows Batch Command article if you haven't done already.
Please have in mind that if you are executing a code coverage tool or another tool that works with profiler you will need to enable the integration with JustMock. This could be done just once for the build server by opening the Telerik.JustMock.Configuration.exe located at the Library folder under the JustMock installation folder.
If for some reason this does not work for you please provide more detailed information on your exact scenario.
Regards,
Mihail
Progress Telerik