This is a migrated thread and some comments may be shown as answers.

Profiler must be enabled Error

26 Answers 1140 Views

General Discussions

This is a migrated thread and some comments may be shown as answers.

Chris McNear asked on 10 Feb 2012, 07:10 PM

I recently upgraded from JustMock Free Q1 2011 to JustMock Free Q3 2011. Since upgrading I am getting errors on some of my tests.
The errors are as follows.

Test method SPM150.Test.LogBenchmarkValueChangeTest.Test0020LogTransactionCalledWhenValuesDifferentCorrectParmetersVersion1 threw exception:

Telerik.JustMock.MockException: Profiler must be enabled to mock/assert target SPM150ControllerTestBase.get_AssetsServiceMock() method.

My take on this is that somehow JustMock thinks I am trying to use features that are only available in the Paid version....

The way we have our tests architected is that each method in the code that needs to be tested corresponds to a TestClass with all the needed Unit Tests within that test class for testing that method and only that method. We also have a TestClass which acts as our base class for all the other TestClasses for the methods within a particular class in code. This base class goes ahead and Mocks most if not all of the external dependencies (just Mock.Create) that the tests might use within it's TestInitialize method. this way each time a method runs its getting fresh mocks....

So here is an example of the code.
First the Base Class

[TestClass]

public class SPM150ControllerTestBase

{

public IAssetsService AssetsServiceMock { get; set; }

public INavigationService NavigationServiceMock { get; set; }

public ISPM150Service SPM150ServiceMock { get; set; }

public IGlobalData GlobalDataMock { get; set; }

public SPM150Controller Target { get; set; }

[TestInitialize]

public void TestInit()

{

AssetsServiceMock = Mock.Create<IAssetsService>();

SPM150ServiceMock = Mock.Create<ISPM150Service>();

NavigationServiceMock = Mock.Create<INavigationService>();

GlobalDataMock = Mock.Create<IGlobalData>();

Target = Mock.Create<SPM150Controller>(Behavior.CallOriginal, new object[] { AssetsServiceMock, SPM150ServiceMock, NavigationServiceMock, GlobalDataMock, null });

}

Now The class for the method under test. with a failing method...

[TestClass]

public class LogBenchmarkValueChangeTest : SPM150ControllerTestBase

{

private const string PassedSiteNumber = "12345";

private const string PassedUserName = "Hi Bob!";

private const string PassedPrefix = "EQ Item Update";

[TestMethod]

public void Test0020LogTransactionCalledWhenValuesDifferentCorrectParmetersVersion1()

{

var beforeValue = 100.0;

var afterValue = 1002.0;

var expectedActionString = "EQ List Item Benchmark value changed from [100.0] to [1002.0]";

AssetsServiceMock.Arrange(asset => asset.LogTransaction(Arg.AnyString, Arg.AnyString, Arg.AnyString)).OccursOnce();

Target.LogBenchmarkValueChange(PassedSiteNumber, afterValue, PassedUserName, PassedPrefix, beforeValue);

AssetsServiceMock.Assert();

Mock.Assert(() => AssetsServiceMock.LogTransaction(

Arg.Matches<string>(site => site == PassedSiteNumber),

Arg.Matches<string>(user => user == PassedUserName),

Arg.Matches<string>(actionString => actionString == expectedActionString)));

}

Thank you

Edit 1: I was able to determine the issue is related to whether or not the "Paid" version is installed and enabled or not. When I install the trial for the paid version and enable it the exception goes away and things run. I also understand now that you can't mix Fluent Mocking/Assertion with the non fluent its either one or the other for each test.

Apparently something changed between Q1 2011 and Q3 2011 releases that make things we were doing completely fine in Q1 now require the paid version of Q3? Any thoughts?

I would really like to upgrade to the Q3 release as it provides better support for the Fluent Arranging/Asserting (in particular the Fluent Assert method actually lets you pass in parameters and expectations....) But if our tests are breaking because we don't currently have the paid version I can't use it.

Any ideas are greatly appreciated.

26 Answers, 1 is accepted

answered on 08 Mar 2012, 08:42 PM

I am also getting the profile error on the 'Mock.Arrange' statement but am not sure how to fix it

Here is my test.

[Test]

public void Test_GetApplicantByEmailAddress()

{

string emailAddress = "test1@test.com";

AdmissionsEM admissionsEM = Mock.Create<AdmissionsEM>();

Mock.Arrange(() => admissionsEM.Applicants).ReturnsCollection(GetApplicants());

AdmissionsBF admissions = new AdmissionsBF(admissionsEM);

List<Applicant> applicants = admissions.GetApplicants(emailAddress);

Assert.AreEqual(applicants.Count, 1);

Assert.AreEqual(applicants[0].Email_add, emailAddress);

}

answered on 04 Jul 2012, 02:53 PM

Hi there.

I'm facing teh same problem here: Telerik JustMock free 2012 Q2. When I try to Mock a method from any class, the exception is raised. The code snippet:

CalculoFormula c = Mock.Create<CalculoFormula>();

RM.Fop.Calculos.Calculo calc = Mock.Create<RM.Fop.Calculos.Calculo>();

calc.ParametrosExecucao = new RM.Fop.Interfaces.ParametrosExecucaoBase() {CodColigada =1};

RM.Fop.ObjectModel.ObjectBase owner = new RM.Fop.ObjectModel.ObjectBase();

RM.Fop.CalculosBase.FuncionariosBase funcs = new RM.Fop.CalculosBase.FuncionariosBase(null);

calc.FuncionarioCorrente = Mock.Create<FuncionarioBase>(Constructor.Mocked);

calc.FuncionarioCorrente.Chapa = string.Empty;

Mock.Arrange(() => calc.LogWrite(Arg.IsAny<string>())).DoNothing(); // exception raised here

I also noticed that I doesn't make any difference if JustMock is enabled or not: in both cases, the exception "Profiler must be enabled" is raised. Is there something I can do in order to fix this behavior?

Thank you

answered on 26 Jul 2012, 01:55 PM

I have the latest version, but using Reshaper to run the Unit Tests and I get the same error message. Here is the code

namespace UnitTesting.Mocking

{

using System;

using NUnit.Framework;

using Telerik.JustMock;

public interface IClientServerMockingTest

{

void CallMethod(string id, Action<string> status);

}

public class ClientServerMockingTest : IClientServerMockingTest

{

public void CallMethod(string id, Action<string> status)

{

status.Invoke("Worked");

}

public class TestClass

{

[Test]

public void TestMethod1()

{

var clientServer = Mock.Create<ClientServerMockingTest>();

Action<string> action = Console.WriteLine;

// Throws error : Telerik.JustMock.MockException : Profiler must be enabled to mock/assert target ClientServerMockingTest.CallMethod(String,Action`1)

Mock.Arrange(() => clientServer.CallMethod("demo", action)).DoInstead((string id, Action<string> aciton) => aciton.Invoke("faked"));

clientServer.CallMethod("demo", action);

}

answered on 20 Aug 2012, 01:01 AM

I
too am having issues with JustMock when using certain method calls on
arrange.  Replacing return values seems to work however DoInstead is
failing with profiler exception.  I am using Visual Studio 2010 and
Jetbrains Code Coverage tool.  Being able to check my coverage is
essential to writing effective unit tests.  Please look into this!

[TestMethod]

public void TestSendMailHtml()

{

var smtp = Mock.Create<SmtpClient>();

Mock.Arrange(() => smtp.Send(Arg.IsAny<MailMessage>())).DoInstead(() => Console.WriteLine("Sending HTML Message"));

var mailer = new Mailer(smtp);

mailer.SendMail("Subject", "Body", true);

}

answered on 30 Aug 2012, 03:40 PM

Ricky,

I have tried to reproduce the same situation in another workstation. So, I faced the problem again, but I could solve the problem without installing the PEX/MOLES. The trick is to manually set the environment variables as performed by JustMockRunner(decompiled):

info.EnvironmentVariables["COR_ENABLE_PROFILING"] = "0x1"

;

info.EnvironmentVariables[

"COR_PROFILER"] = "{B7ABE522-A68F-44F2-925B-81E7488E9EC0}"

;

info.EnvironmentVariables[

"COMPLUS_ProfAPI_ProfilerCompatibilitySetting"] = "EnableV2Profiler"

;

//info.EnvironmentVariables[

"JUSTMOCK_INSTANCE"] = Process.GetCurrentProcess().Id.ToString();<br><div></div>

I believe everybody knows how do declare those variables on windows settings. If not, here goes a brief instruction set about how to achieve it: http://www.itcsolutions.eu/2010/11/29/set-environment-variables-in-windows-7-for-java/

After doing this, you have to restart Windows and run VS2010.

Without this, JustMock doesn't work in visual studio (at least here, in my computers).

Thank you

answered on 04 Sep 2012, 05:54 PM

Hi Christiano,

Thanks again for your post. It's great that you solved it out.

To further investigate, please also check the application events log for possible errors. If the JustMock profiler is loaded then you should see an event with ID 1022 and type "Information". Please find the attached justmock_log_success.png file for reference. If the JustMock fails to load then you should see an event with ID 1022 and type "Error". Please find the attached justmock_log_error.png file for reference.

In case you see the error 1022 I would recommend to register the profiler DLLs manually. You can run the following commands from command prompt as an administrator:

regsvr32.exe C:\Program Files (x86)\Telerik\JustMock\Libraries\CodeWeaver\32\Telerik.CodeWeaver.Profiler.dll
regsvr32.exe C:\Program Files (x86)\Telerik\JustMock\Libraries\CodeWeaver\64\Telerik.CodeWeaver.Profiler.dll

I am also adding some points to your telerik account.

Kind Regards,
Ricky
the Telerik team

Explore the entire Telerik portfolio by downloading Telerik DevCraft Ultimate.

answered on 03 Oct 2012, 12:35 PM

Hi,

I'm facing thesame problem, using the paid version of JustMock. But I only get these errors when I do a gated check-in.

One of my test results that make the Gated check-in fail:

Test method SwhBilling.Website.Test.Controllers.ServerControllerTest.CreateTest threw exception:
Telerik.JustMock.MockException: Profiler must be enabled to mock/assert target ServerViewModel.get_Articles() method.

The test that fails:

[TestMethod]

public void CreateTest()

{

//Arrange

Mock.Arrange(() => _facade.GetEnabledArticles)

.Returns(_articles);

Mock.Arrange(() => _serverModel.Articles)

.Returns(new Collection<Article>());

//Act

_controller.Create();

//Assert

Mock.Assert(() => _facade.GetEnabledArticles, Occurs.Once());

}

The Method I'm testing:

public ActionResult Create()

{

ServerModel.Articles.AddRange(Facade.GetEnabledArticles);

return View(ServerModel);

}

answered on 29 Oct 2012, 01:56 PM

To everyone who is still getting this message, I would like to give a few tips that I have picked up as I have been using JustMock.

1. Make sure the methods are virtual!!! Even if this is an interface implementation method, make sure the actual method that implements is marked virtual. I found that I received this error quite often when methods weren't marked as virtual, when I then enabled the profiler I would find that tests did not behave as I expected, and the debugging would be way out of whack. Once I marked the methods as virtual I stopped getting this message and the debugger worked as expected.
2. Make your properties (even automatic) virtual as well. Same as above, it just works better when everything is marked virtual.
3. Use the Arrange methods rather than assignments in your unit tests, For whatever reason when you do a straight assignment to a mocked object or an item under test (even if marked with Behavior.CallOriginal) JustMock is doing some stuff behind the scenes to the object and things don't always get assigned properly.
4. If you can avoid static and private methods, do so. I use internal for anything I need to hide. This way I can use the InternalsVisibleTo attribute in my assemvlyInffo.cs file and things work much better without having to use the profiler.
5. Only use DoNothing() on methods that are void. If there is a Returns() call that will cause the method to do nothing and return the value you assign, DoNothing() and Returns() seem to conflict with each other and things go a little wierd when using both on the same method.
6. Don't forget the Behavior.CallOriginal on your "target" object (class under test).

I hope this helps at least someone to get past some of these issues. I have found that many of my issues were due to the level of my understanding of the JustMock API and how I was attempting to use the API incorrectly. As I have learned more, the issues I have been having tend to be more related to actual issues or more "complicated" difficulties (ex. mocking extension methods, and explicit assertion of those methods).

If I can help anyone any further I will do my best to try.

answered on 31 Oct 2012, 02:44 PM

Thanks Mehfuz, I really appreciate it. I have seen that KB article before and had gone through all those steps in the past. Or at least I thought I had. Many of the issues we have had were related to us using the free version back in Q1 of 2011 and then trying to upgrade the versions as they were released. Many times things that worked in older versions didn't work in the newer versions. This is undoubtedly because we were/are doing things incorrectly when it comes to Mocking using JustMock in those projects, but it definitely added confusion. I just wanted to point out some of the things that we realized we were doing wrong in our projects to hopefully help others.