Ivo Stoilov

Using JustMock with NCrunch and xUnit1 leads to unexpected exception

MbUnitContextResolver gets wrongly initialized because of the weak check based on Gallio.Framework.Assertions.AssertionException type presence in the current app domain. Needs to be improved with some additional type check from mbunit assembly, MbUnit.Framework.TestFixtureAttribute for example.
Problem by Ivo Stoilov Status: New Comments: 1 Last update: 2018-08-09T12:28:39 by Daniel Klinger GC
0
Mihail Vladov

Static method with dynamic argument cannot be mocked if the class is in a different assembly than the unit test

Problem by Mihail Vladov Status: In Development Comments: 1 Attachments: 1 Last update: 2018-08-09T08:02:19 by Rositsa Fakalieva
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
Kamen Ivanov
Team Member

Support for named parameters in Mock.Arrange

It would be good if we could use named parameters inside Mock.Arrange method.
Feature Request by Kamen Ivanov Status: In Development Comments: 0 Attachments: 1 Last update: 2018-07-27T11:58:44 by Ivo Stoilov
0
Stefan Dragnev

Arrange return value of `new` expressions

I want to be able to arrange the return value of `new` expressions, like Mock.Arrange(() => new FileInfo()).Returns(mockFileInfo).
Then, I expect that `new FileInfo()` will always return my mock instance.
Feature Request by Stefan Dragnev Status: Completed Comments: 3 Last update: 2018-07-23T13:47:39 by Mihail Vladov
0
Stefan Dragnev

Support interop-related method signatures - pointers, TypedReference and __arglist

Feedback by Stefan Dragnev Status: Approved Comments: 1 Last update: 2018-07-23T13:39:42 by Mihail Vladov
0
Калоян Которов

Expectations on specific instance using future mocking

Current behavior:
Mock.Arrange(xxx).IgnoreInstance(); //mock all future instances of the type on which I set an expectation.


Feature Request:
Mock.Arrange(xxx).IgnoreInstance().Next(); //mock the next instance of the type on which I set an expectation.

...and even better...

Mock.Arrange(xxx).IgnoreInstance().Skip(3).Next(); //mock the 4th instance of a type on which I set an expectation.
Feature Request by Калоян Которов Status: Approved Comments: 0 Last update: 2018-07-23T13:31:12 by Mihail Vladov
0
Phillip Moore
0
Stefan Dragnev

Support Runtime Callable Wrapper (RCW) future/partial mocking

I'm a user that is refactoring a legacy system which has a certain component to which I do not have the source. It uses COM interop heavily. I would like to be able to future-mock instances of RCW's so that I can write tests for that component.
Feedback by Stefan Dragnev Status: Approved Comments: 1 Last update: 2018-07-23T13:16:52 by Mihail Vladov
0
Displaying items 1 - 10 of 63