In the code as written I get an error:
Occurrence expectation failed. Expected at least 1 call. Calls so far: 0
Arrange expression: () => test.Test(family1).

However, when I change the code to not have Family based on Collection<Individual> it works.

This does not seem correct.  Is this a bug, or am I missing something on how JustMock is matching these parameters?

Eric Gurney

Greetings,

I downloaded JuckMocked, open the VB.NET solution, did a build and got a good deal of errors in various statements in regards to Lambda inline functions. Now I could go in and figure them out easily but I am not here for that but instead to evaluate this product hence my thread.

BTW: No issues with the C# solution.

Open with VS2012 Ultimate

Am I correct in saying that when using the AutoMocking container to assert a call on a dependency, you *have* to create some form of expectation which is then asserted (e.g. with AssertAll), rather than just defining the assertion at the end?

For example, the following works:
[TestMethod]
public void Test()
{
 var c = new MockingContainer<Target>();
 c.Arrange<ITargetDependency>(x => x.ShouldBeCalled());

 c.Instance.WorkYourMagic();

 c.AssertAll(); // will fail if WorkYourMagic does not call ITargetDependency.ShouldBeCalled()
}

However, this does not...
[TestMethod]
public void Test()
{
 var c = new MockingContainer<Target>();

 c.Instance.WorkYourMagic();

 c.Assert<ITargetDependency>(x => x.ShouldBeCalled()); // Always claims WorkYourMagic does not call ITargetDependency.ShouldBeCalled()
}

Regards,
Nick

The following works:

This doesn't work:

On another forum I found out how to mock the Operational context in this snippet

what I want to do is mock the endpoint in it now, My unit test here needs to test all aspects and I am having issues actually mocking the endpoint

truthfully I do not know what needs to be mocked or how but I know what I want the end result to be. I just need to be able to get endpoint to not be null and set
retVal = endpoint.Address;
Ive tried so many things that I could not get a result 

The code:

        public static string GetCallerIPAddress()
        {
            string retVal = null;
            if (OperationContext.Current != null)
            {
                MessageProperties prop = OperationContext.Current.IncomingMessageProperties;
                RemoteEndpointMessageProperty endpoint = prop[RemoteEndpointMessageProperty.Name] as RemoteEndpointMessageProperty;
                if (endpoint != null)
                {
                    retVal = endpoint.Address;
                }
            }
            return retVal;
        }

Given the above code, a null reference exception is thrown on line 32.

I am using NInject to do constructor dependency injection.  I have a large hierarchy of classes that take in their dependencies in their constructors as Foo and Bar do above.  I want all of my concrete classes to be instantiated and only have the interfaces get mocked.  In the above example, I want a real Bar constructed and a real Foo constructed but I want IBaz to be mocked.

I am aware that in the above scenario I could just manually construct a Foo, passing in a manually constructed Bar, but in my scenario, the dependency hierarchy is large and complex and interfaces wrap all external (not my code calls).  Is there an easy way to tell the MockingContainer<Foo> that it should mock all interfaces but not mock any concrete classes (actually instantiate them).

As I said, I am using Ninject to instantiate my classes and it does the right thing everywhere.  I understand that the automocking container is backed by Ninject.  Is there a way I can bind certain interfaces/classes to JustMock?  In the above example I could do something like:

kernel.Bind<IBaz>().To<Mock<IBaz>>()?  That way I could just use Ninject to instantiate my object hierarchy, but tell it which interfaces I want it to bind to JustMock mocked instances.

Hi all,

 I was wondering if JusyMock could easily "intercept" object creation and replace them with fakes created on the fly?

I'm trying to unit test a method that, amongs other things, creates an instance of an object of a certain type and then uses it.  The instance is NOT injected into the method and so I cannot control what instance is used inside the method...

I know that some other mocking framework do support Future Objects mocking.  Is it the case with JustMock ?

Thanks for your time,

Vincent Grondin

EDIT:   I think I need the "Weaver" library to accomplish this, can someone from telerik tell me if this library is included in the FREE version of JustMock? 

Hi,

Looking at getting JustMock but have a simple license question. If say in a dev team of 20, only 10 would write unit tests, but the unit tests are in the solution, would the remaining 10 developers that don't have a JustMock license be able to build and run the unit tests?

Thanks for your help

Graham

I'm using Visual Studio 2013 MSTest
JustMock Lite 2014.2.609.3 (via NuGet)

I'm trying to move the "MustBeCalled" expectations to TestCleanup.
Here is an example of code.


If I run the code as is, the test will pass (regardless if line 20 is commented or not).

This can be fixed by moving the Mock.Assert to line 22+ but ideally I would like to "auto call" Mock.Assert at the end of every test.  I thought that adding it to TestCleanup would work but it doesn't appear to do so.

It appears that prior to TestCleanup running, JustMock will clear out the expectations prior to running TestCleanup.
Is there anyway around this?

Why am I doing this?
Because I'd actually like to write tests like this.


Of course my actual test classes will be more complex. But this approach allows me to Mock out MustBeCalled expectations in a more readable manner.  Currently, the test author will have to remember to call Assert the _svc class (or _assertList) at the end of every TestMethod, but was hoping for a more maintainable solution.

Thanks

If this has been answered already you can just direct me there...

In the method i am working on I am trying to mock a "checkpoint".

the line of code is this....    if (File.Exists(filePath)){
rest of code is here
}
I need to mock this so the program just moves on regardless of if there is a file there or not.

Any suggestions?