mrsuau627
commented
3 years ago I have the same request. We're using xUnit and Moq and have the same issue.
The constructor generates the mock dependencies like this:
_systemService = new Mock<ISystemService>().Object;
instead of
_systemService = new Mock<ISystemService>();
As a result, when we go to fill in one of the Method stub functions, we can't use the mocks effectively because we can't set them up for the specific tests.
Seems like a better approach would be to define the mocks as actual mocks like:
private Mock<ISystemService> _systemService;
and then in the test you would have the ability to Setup the mock and then use it as _systemService.Object
mattwhitfield
Currently, class dependency is generated as interface variable.
I'd like an option to generate dependency as mocked interface. Reason is I want to setup and verify mocked method later
Sample source code: public class Parent { private IChild child; public Parent(IChild child) { this.child = child; } public void DoSomething() { this.child.DoSomething(); } }
Expected unit test:
public class ParentTests { private Parent _testClass; private Mock\<IChild> _childMock;
[TestInitialize] public void SetUp() { _childMock = new Mock\<IChild>(); _testClass = new Parent(_child.object); } ... }
Actual Unit test generated:
public class ParentTests { private Parent _testClass; private IChild _child;
[TestInitialize] public void SetUp() { _child = new Mock().Object;
_testClass = new Parent(_child);
}
...
}