Robert Welters

JustMock should support .NET Core

Feature Request by Robert Welters Status: Approved Comments: 4 Last update: 2018-11-15T15:19:03 by Kim Hugener Ohlsen
0
Michael Crawford

Don't block Visual Studio Live Share

Creating a share link with Visual Studio Live Share does not work if you have the JustMock profiler enabled. We specifically have to disable the JustMock profiler in order for VS Live Share to create sharing links. This has been reproduced by several different members of our team.

Could this please be looked into? Thanks!
Problem by Michael Crawford Status: Approved Comments: 3 Last update: 2018-10-25T18:52:51 by Michael Crawford
0
Troy Schmidt

Allow future mocking of an entire class

Allow future mocking of an entire class, including a default of DoNothing() for all methods in the class, rather than requiring each method to be future mocked separately.
Feature Request by Troy Schmidt Status: Approved Comments: 0 Last update: 2018-10-12T08:32:54 by Mihail Vladov
0
Mihail Vladov

Implement support for passing "out" and "ref" parameters for nonpublic API

Currently, there is no out of the box support for passing "out" and "ref" parameters for nonpublic API.
Feedback by Mihail Vladov Status: Approved Comments: 0 Last update: 2018-10-08T10:50:46 by Mihail Vladov
0
Ivo Stoilov

Add support for "registry free profiler startup" to JustMockRunner

The main point behind this request is to add new command line option to JustMockRunner in order to enable profiler without need for being registered, more details about this feature can be found on MSDN at https://msdn.microsoft.com/en-us/library/ee471451(v=vs.100).aspx
Feature Request by Ivo Stoilov Status: Approved Comments: 0 Last update: 2018-10-08T10:43:13 by Mihail Vladov
0
Ivo Stoilov

Mock assert doesn't fail when there are multiple mocks with occurrence expectations that are not satisfied

If there are more that one mock objects existing in the test, Mock.Assert wrongly succeeds while evaluating arrangements for each mock, but not the very first one. This is a regression compared to an older version from 2012. The following sample demonstrates the case:
public interface IFoo
{
    void Bar();
}

[TestClass]
public class UnitTest1
{
    [TestMethod]
    public void TestMethod1()
{
        var bar = Mock.Create<IFoo>();
        Mock.Arrange(() => bar.Bar()).OccursOnce();

        var foo = Mock.Create<IFoo>();
        Mock.Arrange(() => foo.Bar()).OccursOnce();

        Mock.Assert(foo); // Would wrongly succeed
        Mock.Assert(bar); // Would fail as expected
    }
}
Problem by Ivo Stoilov Status: Approved Comments: 0 Last update: 2018-10-02T10:56:04 by Mihail Vladov
0
Mihail Vladov

Research how JustMock profiler can run in an isolated container like Docker or hosted VSTS

Docker is a container acting like an isolated environment. Research how the JustMock profiler can be registered into such container.
Hosted VSTS should work on the same principle. Research how the registry could be accessed through VSTS extension or other tools.
Feedback by Mihail Vladov Status: Approved Comments: 2 Last update: 2018-09-25T10:23:20 by Mihail Vladov
0
Lyubomir Rusev

Call to Arrange method wrongly mocks property used as parameter

A class property get wrongly mocked when used as parameter for arranging other class methods. The following sample demonstrates the scenario:

class Foo
{
public string Prop{ get; set; }

public void Bar(string val)
{
}
}

[TestMethod]
public void Sample()
{
var sut = Mock.Create<Foo>(Behavior.CallOriginal);

Mock.Arrange(() => sut.Bar(sut.Prop)).DoNothing();
}
Problem by Lyubomir Rusev Status: Approved Comments: 0 Last update: 2018-09-13T06:41:42 by Mihail Vladov
0
Ivo Stoilov

Calling async task of mocked object results in unexpected behavior or exception

Mocking an async calls alse triggers hidden mocking of the return type. Depending of the type it might cause unexpected behavior or exception.
Problem by Ivo Stoilov Status: Approved Comments: 0 Last update: 2018-08-07T08:00:10 by Ivo Stoilov
0
Mihail Vladov

Mocking DateTime.UtcNow fails in async test cases

On slow machines, sometimes arrangements lose their context and the expected mocked return value for DateTime.UtcNow fails.
Problem by Mihail Vladov Status: Approved Comments: 0 Last update: 2018-08-06T07:41:38 by Mihail Vladov
0
Displaying items 1 - 10 of 23