Unplanned
Last Updated: 17 Sep 2021 17:27 by ADMIN
Created by: Alan
Comments: 2
Type: Feature Request
2
I am in the process of building an internal developer platform on kubernetes. Historically, in order to run justmock on build servers we pointed to a special location of the windows registry for accessing the DLL. In kubernetes, the build runners are kubernetes nodes. Is there a preferred way to run these tests in this environment? I can provide more details if it is helpful or valuable. Historically, we used Azure Devops build agents in this new world dotnet test is being run in Linux gitlab agents and not windows. I would have chosen linux in the dropdown but wasn't available.
Completed
Last Updated: 16 Sep 2021 08:43 by ADMIN
Created by: Mihail
Comments: 1
Type: Feature Request
9
Implement support for executing JustMock tests on Linux
Completed
Last Updated: 16 Sep 2021 08:42 by ADMIN
Created by: Mihail
Comments: 1
Type: Feature Request
0
JustMock should have support for the upcoming official release of Visual Studio 2022
Planned
Last Updated: 10 Sep 2021 14:15 by ADMIN

Currently, when the JustMock profiler is enabled it provides a performance hit on the test execution. This effect is expected because a profiler is involved.

What we can do is find a more optimized way of instrumenting the methods.

Planned
Last Updated: 10 Sep 2021 14:15 by ADMIN
Created by: Ivo
Comments: 0
Type: Feature Request
1

C# 8 introduces default interface method implementations. Attempt to mock such methods with JustMock in elevated mode fails. The following example illustrates the issue:

public interface IMyInterface
{
    int IntProperty { get => 0; }
}


[TestClass]
public class UnitTest1
{
    [TestMethod]
    public void TestMethod1()
    {
        var mock = Mock.Create<IMyInterface>();
        Mock.Arrange(() => mock.IntProperty).Returns(1);

        Assert.AreEqual(1, mock.IntProperty);
    }
}

 

 

 
Unplanned
Last Updated: 19 Aug 2021 08:02 by ADMIN
Created by: Mihail
Comments: 0
Type: Feature Request
0

Allow the developer to create custom behaviors and use them in an arrangement. Something like the following:

            Mock.Arrange(() => foo.CalcData(Arg.AnyInt, Arg.AnyInt), new IBehavior[]
            {
                new LogInvocation(),
                new ReturnBaseOrDefaultValue(),
            });

Unplanned
Last Updated: 19 Aug 2021 07:54 by ADMIN

The new public API should allow the developer to access the invocations for a particular arrangement. Something like the following:

IEnumerable<IInvocaiton> invocations = foo.GetInvocationsFor((x) => x.CalcData(2, 2));

Unplanned
Last Updated: 19 Aug 2021 07:50 by ADMIN

Implement a new public API that will allow the developer to iterate over all invocations of mock arrangements. Something like the following:

IEnumerable<IInvocaiton> invocations = Mock.Invocations;

Unplanned
Last Updated: 13 Jul 2021 07:34 by ADMIN
Create a Mock.Assert(); or a similar method that will verify all mock objects arranged for the current test method complies with the set expectation.
Unplanned
Last Updated: 17 May 2021 08:38 by ADMIN
Created by: Mihail
Comments: 0
Type: Feature Request
0
Integration with dotCover is only available through Telerik.JustMock.Configuration.exe, which works with the machine's registry and needs JustMock to be installed. This approach is not applicable to cloud-based build agents and therefore we need an integration that does not require the installation of JustMock.
Completed
Last Updated: 17 May 2021 08:10 by ADMIN
Trial period expiration disables the essential functionality inside JustMock extension menu, but there is no clear sign for the reason. This item is about improving this situation, by making the trial expiration explicitly and easily visible to the user.
Completed
Last Updated: 10 Feb 2021 11:41 by ADMIN
Implement support for code coverage in the JustMock VSTest v.2 Azure Pipeline task similar to the code coverage option available in VS Test task.
Unplanned
Last Updated: 10 Feb 2021 10:47 by ADMIN
Created by: Toshio
Comments: 1
Type: Feature Request
0
An attempt to use future mocking fails. The attached sample demonstrates the issue.
Completed
Last Updated: 02 Feb 2021 09:28 by ADMIN
Created by: Mihail
Comments: 3
Type: Feature Request
0
JustMock should support .NET 5
Declined
Last Updated: 01 Feb 2021 09:35 by ADMIN
I am using Visual Studio 2015, Crystal Reports 12.0.2.  When running from Visual Studio in debug mode or not, the application hangs on the statement "new ReportDocument()".  ReportDocument is a class defined in CrystalReports.

When I disabled the JustMock Profiler, this statement no longer hung.

Just FYI.  Hopefully others will see this.
Completed
Last Updated: 03 Nov 2020 13:28 by ADMIN
The JustMock profiler should be added to the commercial NuGet package distributed from the Telerik private NuGet server.
Completed
Last Updated: 21 Oct 2020 09:38 by ADMIN
Currently, JustMock DebugWindow service is using a hardcoded port range which might conflict with other existing TCP services.
Unplanned
Last Updated: 18 Sep 2020 08:00 by ADMIN
Created by: Dan Avni
Comments: 1
Type: Feature Request
0
After creating a future mock for some method in an object in which I also specify the mock must be called, there is no way to assert that the mock was actually called. Using Mock.Assert on the test method always passes even when the mocked method was not called.
Completed
Last Updated: 17 Sep 2020 09:24 by ADMIN

The issue is present when JustMock extension is installed and the debugger is launched inside unrelated projects, for example, a blank console app. The extension should detect JustMock references from project settings and automatically disable this feature when it becomes inapplicable. Optionally the extension could give the way to explicitly disable the debug window from popping up by toggling the menu item.

Completed
Last Updated: 17 Sep 2020 09:18 by ADMIN
Currently, the Debug Window could be used only with one instance of Visual Studio. The goal of this feature is the Debug Window to support multiple independent instances of Visual Studio.
1 2 3 4 5