Thanks for bringing these questions up.
> Will tests start failing if I disable the "Enable Profiler" setting?
Only the "elevated" tests will fail if you disable JustMock from the Visual Studio menu. The "elevated" tests are those which mock static types and members, sealed types, non virtual members and so on. The other tests which mock interfaces, virtual members, etc. will not fail.
Actually the elevated tests might not fail at all, if you had already run the tests prior to disabling JustMock, as most of the test runners keep the test runner process alive after the first run and thus JustMock's profiler will be already enabled in the test runner process.
> How do I control this setting on the CI build server?
It depends on the CI server. We've provided integration tasks for MSBuild and NAnt and you can get more information here on how to use them:
You can also check this forum post on how to use JustMock in TFS 2010:
For other CI build servers you'll need to write a custom integration task specific for the build server which you're using. Generally this should be easy as the only thing you need to do is to set three environment variables before the build servers runs the tests. These are the variables and their respective values:
> The profiler should be dynamically loaded if the unit tests demanded the profiler. AFAICT, this information should be contained in the unit tests
Actually that's what we do. Should you have some issues with such scenario (tests mocking interfaces or virtual members which are failing with disabled profiler mode), please send us a separate support request because most probably this is a bug which need to fix.
Hope this infromation helps.
All the best,
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items