Questions on JustMock Forum

1 answer

456 views

Is there a NuGet package for JustMock non-lite? Since the features of non-lite require a profiler it seems that you wouldn't be losing anything by making the .NET assemblies for the non-lite version available on NuGet since users would still have to purchase a license to actually use the features provided in the assembly.

Myself and one of my peers (we'll call him Bob) are working together on a project. I install JustMock to the default install path (C:\Program Files (x86)\Telerik\JustMock) while he installs to D:\Programs\JustMock. I keep my source code in C:\Users\Micah\Source\GitHub\awesome and he stores it in C:\source\awesome. I add JustMock to our UnitTest project (in the awesome repo) by adding a reference to C:\Users\Micah\Documents\Source\dotnet_agent\Agent\packages\JustMock.2013.3.819\lib\Net35\Telerik.JustMock.dll. I commit and push this change to GitHub and then Bob pulls the change down. He then attempts to build and receives an error saying the assembly couldn't be found.

There appear to be a few solutions, though none of them seem particularly clean:
1. Copy Telerik.JustMock.dll to our repo and reference it there.
2. Have all developers copy Telerik.JustMock.dll to the GAC.
3. Have all developers use the same install path for JustMock.
4. Have all developers use the same install path for JustMock and the source code.

Problems with each:
1. Telerik.JustMock.dll has to match the version of the profiler that is installed. The same problem would occur with a NuGet package.
1. I have to know which of the JustMock\Libraries assemblies I need. Right now I am just using JustMock.dll but I have only scratched the surface of JustMock, will I need others like JustMock.Container or Practices.Unity?
2. It is easy to forget to do this when building out a new machine or onboarding a new developer.
2. Every time a user upgrades JustMock they have to re-copy the assemblies or risk versioning related failures.
3,4. Everyone sets up their workspace differently, some developers may not even be able to match the folder structure of others (perhaps their whole OS and applications are on D drive or they are running x86 version of the OS).

A NuGet package still has the versioning issue but at least it is one that can be reported as an intelligible error at runtime and it eliminates all of the other problems.

Assuming a NuGet package isn't available, what solution is recommended in the meantime? I am most fond of #1 but I don't know which assemblies to copy. Insight wanted.

General Discussions

answered on 22 Aug 2013

1 answer

102 views

Behavior.Strict OccursNever instead of throwing an exception?

We have some mission critical code that catches all exceptions and recovers from them in various ways. I would like to be able to use Mock.Create<MyClass>(Behavior.Strict) so that I can know that none of the methods on MyClass are being called besides the ones I explicitly Mock.Arrange. However, this results in the methods throwing exceptions which are then caught by my application and recovered from so I never see them.

I would like something like this, but where I didn't have to manually arrange every method on the class and instead have some Behavior that I could give to Mock.Create that would result in all of the arranges being auto-generated. I could then manually arrange anything I didn't want to have OccursNever on, just like you can override the exceptions thrown by Behavior.Strict.

class MyClass

{

public void Method1() { }

public void Method2() { }

public void Method3() { }

}

class ClassUnderTest

{

public void DoSomething(MyClass myClass)

{

myClass.Method3();

}

[Test]

void MyClass_methods_are_never_called()

{

// ARRANGE

var myClass = Mock.Create<MyClass>();

Mock.Arrange(() => myClass.Method1()).OccursNever();

Mock.Arrange(() => myClass.Method2()).OccursNever();

Mock.Arrange(() => myClass.Method3()).OccursNever();

// ACT

var classUnderTest = new ClassUnderTest();

classUnderTest.DoSomething(myClass);

// ASSERT

Mock.Assert(myClass); // this will fail

}

General Discussions

answered on 21 Aug 2013

0 answers

47 views

Profiled tests fail when run together.

Nevermind. It was a problem with having a static that was being re-used, not a problem with JustMock. (please delete this post if possible)

General Discussions

asked on 21 Aug 2013

8 answers

206 views

JustMock+NUnit+dotCover+TeamCity

Hello,

similiary to Alexander in http://www.telerik.com/community/forums/justmock/general-discussions/justmock-dotcover-teamcity-problem.aspx thread i'm trying to make satup for unit test running nunit+justMock+dotcover, and i'm facing problems similiar to Alexander's, thus i created simple test as suggested in mentioned thread:

Assert.IsTrue(Mock.IsProfilerEnabled);

which results in following output:

[16:41:15][Step 6/7] NuSoft.Printer.Rs232.Tests.dll

[16:41:15][NuSoft.Printer.Rs232.Tests.dll] NuSoft.Printer.Rs232.Tests.PrinterTest.AssertStringPrinted

[16:41:15][NuSoft.Printer.Rs232.Tests.PrinterTest.AssertStringPrinted] Test(s) failed. Expected: True

But was: False

[16:41:15][NuSoft.Printer.Rs232.Tests.PrinterTest.AssertStringPrinted] Test(s) failed. Expected: True

But was: False

at NUnit.Framework.Assert.That(Object actual, IResolveConstraint expression, String message, Object[] args)

at NUnit.Framework.Assert.IsTrue(Boolean condition)

at NuSoft.Printer.Rs232.Tests.PrinterTest.CheckProfiler() in c:\TeamCity\buildAgent\work\64cb9cb36a4269ed\NuSoft.Printer.Rs232.Tests\PrinterTest.cs:line 18

at NuSoft.Printer.Rs232.Tests.PrinterTest.AssertStringPrinted() in c:\TeamCity\buildAgent\work\64cb9cb36a4269ed\NuSoft.Printer.Rs232.Tests\PrinterTest.cs:line 24

I followed manual http://www.telerik.com/help/justmock/integration-teamcity.html section Integrating JustMock within TeamCity using MS Test or NUnit build steps with dotCover and Profiler is linked to dotCover (the only one installed is the one bundled with TeamCity) and JUSTMOCK_INSTANCE=1 variable is present in build parameters.

tests run in VS2012, also when configured accordingly to Integrating JustMock within TeamCity using MS Test or NUnit build steps.

Telerik.JustMock - 2013.2.611.0
TeamCity - 7.1.5 (build 24400)

is there any thing that can be done in order to configure justmock to run on teamcity with nUint and dotCover?

General Discussions

answered on 19 Aug 2013

2 answers

405 views

How to Mock an OUT variable

Hello,

I have the following code:

var mockDocumentRepository = Mock.Create<IDocumentRepository>();

Mock.Arrange(() => mockDocumentRepository.FetchDocumentsByListCriteria(Arg.IsAny<ListCriteria>(), Arg.AnyInt, Arg.AnyInt, out virtualCount)).Returns(GetFakeDocumentListWithChildren_OneChildLevel());

As you can see I have an out parameter, I have not figure out how to mock virtualCount, what I did is created a variable in my test method which I do not like. Can you provide an example of how to do that?

Also, if you can provide an example how to mock a ref parameter as well please?

Also, how can Mock a delegate that I pass into method under test, right now I create a method in my test class that matches the delegate signature and pass that across, is there a better option?

I am using 2013.2.701.0 version.

General Discussions

answered on 19 Aug 2013

4 answers

128 views

Unit Test not using Mocked object

I'm using/implementing JustMock for the first time. I've watched the webnair, but I can't seem to get the Mocked object working properly. We have a full paid version of JustMock.

I have an internal database access layer object, "OperationsData", and an "ComponentException" object with a private constructor. I'm trying to write the unit test method for the Persist method of the ComponentException object. The unit tests are all in a separate project so the internal class and the private constructor use a "_Accessor".

When I run the unit test it complains that OperationsData connection string isn't instantiated. Why isn't it just using the mocked object and return the expectedExceptionId that I want? Thanks.

This is the ComponentException.Persist() ...

public void Persist()

{

try

{

OperationsData data = new OperationsData();

this.ExceptionId = data.PersistException(this.Id, this.ExceptionCode, this.ComponentName, this.SeverityIndicator.ToString(), this.ProcessName, this.BusinessExceptionDetail, this.StackTrace);

}

catch (Exception ex)

{...}

}

This is the UnitTest...

[TestMethod()]

public void SuccessfulPersistTest()

{

/// Arrange

long expectedExceptionID = 12345;

long ID = 678901;

string exceptionCode = string.Empty;

string componentName = string.Empty;

string severityIndicator = string.Empty;

string processName = string.Empty;

string businessExceptionDetail = string.Empty;

string stackTrace = string.Empty;

OperationsData_Accessor operationsData = new OperationsData_Accessor();

operationsData.Arrange(od => od.PersistException(ID, exceptionCode, componentName, severityIndicator, processName, businessExceptionDetail, stackTrace))

.IgnoreInstance()

.Returns(expectedExceptionID);

///Action

ComponentException_Accessor target = new ComponentException_Accessor();

target.Persist();

///Assert

Assert.AreEqual(expectedExceptionID, target.ExceptionId);

operationsData.Assert();

}

PS. I also tried...

OperationsData_Accessor operationsData = Mock.Create<OperationsData_Accessor>(Constructor.Mocked);

General Discussions

answered on 14 Aug 2013

12 answers

289 views

Is JustMock threadsafe?

I'm calling a mock on multiple threads. Sometimes this works just fine. But sometimes the mock call fails with a System.ArgumentException "An item with the same key has already been added.". Here's the end of the stack trace: -

at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)

at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)

at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)

at . . (MethodInfo )

at . . (MockInvocation )

at . .Intercept(MockInvocation )

at . .Intercept(IInvocation )

Now I'm not using any dictionaries in my code - is it possible that this is happening somewhere inside the mock?

JustMock Free Edition

answered on 14 Aug 2013

1 answer

166 views

Exception trying to mock UserProfileManager

I'm trying to create a mock version of UserProfileManager in order to effectively unit test a Sharepoint 2010 Web Part
Every time I run this code, I get the the exception being thrown below. I've verified that the feature works when I debug the code that calls UserProfileManager on the Sharepoint machine - two different Sharepoint machines, in fact.
Here is the code in question:

var _mockServiceContext = Mock.Create<SPServiceContext>();

var _mockUserProfileManager = Mock.Create<UserProfileManager>(new object[] {_mockServiceContext});

Unable to create instance of class SharePoint.MyWebPart.Test.MyTest. Error: Microsoft.SharePoint.SPException: The trial period for this product has expired..
    at Microsoft.Office.Server.UserProfiles.ProfileManagerBase.ValidateLicensing()
   at Microsoft.Office.Server.UserProfiles.ProfileManagerBase..ctor(SPServiceContext serviceContext)
   at Microsoft.Office.Server.UserProfiles.ProfileManagerBase..ctor(SPServiceContext serviceContext, Boolean ignorePrivacy)
   at Microsoft.Office.Server.UserProfiles.UserProfileManager..ctor(SPServiceContext serviceContext, Boolean IgnoreUserPrivacy, Boolean backwardCompatible)
   at Microsoft.Office.Server.UserProfiles.UserProfileManager..ctor(SPServiceContext serviceContext)
   at Castle.Proxies.UserProfileManagerProxy..ctor(IEventsMixin, IMockReplicator, IMockMixin, IInterceptor[], SPServiceContext)
   at DynamicMethod_6f2d60ffa4f94cb4ba57556150461ef9(Object[])
   at ...()
   at ..[](Func`1 )
   at ..(Type , Object[] )
   at ..(Type , List`1 , Type , Object[] )
   at ..(Type , Type[] , ProxyGenerationOptions , Object[] , IInterceptor[] )
   at Telerik.JustMock.Core.MocksRepository.Create(Type , Object[] , IEnumerable`1 , IEnumerable`1 , IEnumerable`1 , Type[] , Boolean , Boolean , IEnumerable`1 )
   at ..Create(MocksRepository , Type , Object[] , Nullable`1 , Type[] , Nullable`1 , IEnumerable`1 , List`1 , List`1 , List`1 )
   at Telerik.JustMock.Mock..()
   at ..[](Func`1 )
   at Telerik.JustMock.Mock.Create(Object[] args)

Has anyone else seen this issuue?

General Discussions

answered on 14 Aug 2013

9 answers

190 views

Mock.Create<SPServiceContext>() causes Serialization exception

I'm trying to write some unit tests for a Sharepoint 2010 Webpart that uses UserProfile manager.
In order to mock UserProfileManager, I also need to mock SPServiceContext.

When I try to assign my mock variable, like this:

_mockServiceContext = Mock.Create<SPServiceContext>();

The following exception is thrown:

Type 'Telerik.JustMock.MockException' in assembly 'Telerik.JustMock, Version=2013.1.507.0, Culture=neutral, PublicKeyToken=721b6c5bc0326b3a' is not marked as serializable.

Any idea what I'm doing wrong?

General Discussions