In Development
Last Updated: 26 May 2020 08:21 by ADMIN
Debug Window affects performance in local test run when not debugging. The expected behavior is the Debug Window to not be loaded in this scenario.
Unplanned
Last Updated: 20 May 2020 11:27 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.
Completed
Last Updated: 20 May 2020 10:55 by ADMIN
In Development
Last Updated: 20 May 2020 10:40 by ADMIN
Created by: Mihail
Comments: 0
Type: Feature Request
0
JustMock should support .NET 5
Unplanned
Last Updated: 14 May 2020 11:23 by ADMIN
Created by: Robert
Comments: 0
Type: Bug Report
1
The test execution of a test hangs forever. Please see the attached VS 2019 Solution that contains one TestMethod.

R2 2020 is unusable. I reverted back to R1 and there the tests succeed in less than a second.
Unplanned
Last Updated: 22 Apr 2020 15:26 by ADMIN
The Add/Update JustMock reference is shown for .NET Core projects but without implementation it does nothing.
Unplanned
Last Updated: 07 Apr 2020 12:07 by ADMIN
In some cases, the working directory of the test execution needs to be changed to a dedicated path. Currently, it is not possible out of the box, as a workaround can be used start command.
Unplanned
Last Updated: 06 Apr 2020 09:12 by ADMIN

Currently, the support for code coverage in the JustMock Azure Pipeline task includes only projects targeting .NET Framework.

Implement support for projects targeting .NET Core.

Unplanned
Last Updated: 02 Apr 2020 17:25 by ADMIN

Having the following COM interop class

[ClassInterface(ClassInterfaceType.None)]
[Guid("86332C4E-0BDE-46EC-94C5-0A946C33C682")]
[TypeLibType(TypeLibTypeFlags.FCanCreate)]
public class MyComObjectClass : IMyComObject, MyComObject
{
    public MyComObjectClass();

    [DispId(1)]
    public virtual string Echo(string message);
}

and the sample class that uses it:

public class MyComObjectClassProxy
{
    public string Echo(string message)
    {
        IMyComObject itf = null;
        try
        {
            itf = new MyComObjectClass();
            return itf.Echo(message);
        }
        finally
        {
            if (itf != null)
            {
                Marshal.ReleaseComObject(itf);
            }
        }
    }
}

When I try to call the arranged constructor I am getting an error "Cannot create instances of type requiring managed activation", the unit test code:

[TestMethod]
public void TestMethod1()
{
    var mock = Mock.Create<MyComObjectClass>();
    Mock.Arrange(() => new MyComObjectClass()).Returns(mock);

    var sut = new MyComObjectClassProxy();
    var actual = sut.Echo("Message");

    Assert.AreEqual(string.Empty, actual);
}
Completed
Last Updated: 24 Mar 2020 16:37 by ADMIN

Hi

When enabling JUSTMOCK Profiler it stops a MS rdlc report to render.

I have attached a simple sample demonstrating the error.

The error that the render gives back is the following.

The definition of this report is not valid or supported by this version of Reporting Services. The report definition may have been created with a later version of Reporting Services, or contain content that is not well-formed or not valid based on Reporting Services schemas. Details: Deserialization failed: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B) Line 2, position 2.

I have tried to different target version of the .NET framework 4.5.2; 4.6.2, different platform targets "ANY,x86,x64", different VS IDE "2012, 2015", different Microsoft.ReportViewer.WinForm  ver. 11,12,14

Completed
Last Updated: 24 Mar 2020 16:25 by ADMIN
Having a sample configuration:
<DataCollector friendlyName="Code Coverage Wrapper">
  <Configuration>
    <SinkDataCollector friendlyName="Code Coverage" IsLinked="true" />
  </Configuration>
</DataCollector>
Currently, the attribute names are not consistent in the naming convention which might lead to errors.
Unplanned
Last Updated: 21 Feb 2020 11:53 by ADMIN
Created by: Toshio
Comments: 0
Type: Bug Report
0
An attempt to use future mocking fails. The attached sample demonstrates the issue.
Completed
Last Updated: 20 Feb 2020 07:05 by ADMIN

Hello,

According to the JustMock documentation, to validate a method on the mock was called it should be done like so:

[TestMethod] 
public void ShouldThrowExceptionWhenMustBeCalledSetupIsNeverInvoked() 
{ 
    // Arrange 
    var foo = new Foo(); 

    Mock.Arrange(() => foo.Execute()).MustBeCalled(); 

    // Assert 
    Assert.Throws<AssertFailedException>(() => Mock.Assert(foo)); 
}

When I do that, the application fails to compile saying the type AssertFailedException does not exist, even though I have the using statement for the Telerik.JustMock assembly at the top of my file. If I try to fully qualify it like so:

Assert.Throws<Telerik.JustMock.Xunit.AssertFailedException>

I get the same message for the "Xunit" namespace.

I know that the type should exist since when I run the test asserting a different type of Exception, the test fails saying it expects an exception of type Telerik.JustMock.Xunit.AssertFailedException.

I am attaching a couple of images that illustrate the problem.

Thank you.

 

Completed
Last Updated: 20 Feb 2020 07:04 by ADMIN
When I try to create a new JustMock test project for .NET Framework the version of .NET Framework that I select is not respected. The result is that the used version of .NET Framework is always 4.5.2
Completed
Last Updated: 20 Feb 2020 06:56 by ADMIN

Currently, there are a lot of JustMock project templates with different targeted categories. There are templates targeting just one search category and there are other templates targeting different categories.

Optimize the templates to be available in all relevant search categories and lower their number.

Completed
Last Updated: 20 Feb 2020 06:53 by ADMIN

The integration does not work as expected when the tests are run on the command line outside Visual Studio via dotnet test command. The coverage is used as Microsoft.CodeCoverage NuGet package.

 

 
Completed
Last Updated: 05 Feb 2020 10:56 by ADMIN
Asynchronous test execution might be run in a separate thread (it depends of the environment and it is completely transparent) which causes arrangements to lose their context. That is why the expected mocked return value for DateTime.UtcNow calls the original code and finally the test fails.
Completed
Last Updated: 15 Jan 2020 14:57 by ADMIN
Just like the core mocking API has ArrangeSet/AssertSet methods, so should the MockingContainer have them.
Completed
Last Updated: 15 Jan 2020 14:56 by ADMIN

Implement integration between JustMock and the code coverage provided by Visual Studio for .net core applications.

Steps representing the missing feature:

Create a .net core test project.

Include JustMock tests.

Execute the tests with code coverage provided by Visual Studio Enterprise.

The tests fail with a message pointing the integration between JustMock and the code coverage tool.
Completed
Last Updated: 15 Jan 2020 09:58 by ADMIN
The JustMock tests are failing when the "Test platform version" option in the JustMock VSTest v.2 task is set to value "Installed by Tools Installer".
1 2 3 4 5 6