microsoft-fakes

class Parent{ public string Name{ get; set; } } class Child :Parent{ public string address{ get; set; } } [TestClass] class TestClass{ [TestMethod] public void TestMethod() { var c = new Fakes.Child(); c.addressGet = "foo"; // I can see that c.NameGet = "bar"; // This DOES NOT exists } } How can I set the "name" in the above code sample? The generated class for Parent will have a constructor that looks like: ShimParent(Parent p) . All you need to do is: var child = new ShimChild(); var parent = new ShimParent(child); And set the appropriate values on the respective Shim's. You'll have to

When I began using Microsoft Fakes, I was excited to start shimming some .NET methods. I was lead to believe that I would be able to shim ANY .NET method, static or not: http://msdn.microsoft.com/en-us/library/hh549176.aspx . However, I've been trying to shim some of the methods in TcpClient and only stubs are created, which does me no good, since I want to be able to change some of the methods to return my own data rather than depending on a live TcpClient to give me data. I'm open to any suggestions on how to do this if there is another way beyond Microsoft Fakes. EDIT: Adding code to

I have Visual Studio 2015 Enterprise and discovered that I cannot compile almost any of our existing 2013 projects. Further investigation reveals that Visual Studio 2015 isn't able to generate fakes for types that were fine in Visual Studio 2013. Consider the following steps to reproduce: Create a unit test project targeting .NET 4.5 Right-click on "System" in the references tab and choose "Add Fakes Assembly" To eliminate the noise for this example, edit the subsequent "System.fakes" file: <Fakes xmlns="http://schemas.microsoft.com/fakes/2011/" Diagnostic="true"> <Assembly Name="System"

I'm trying to set up automated builds and unit testing for a project which uses the Fakes library for it's unit tests. The project builds and tests fine on my Windows 10 PC (VS 2017 Enterprise installed), however using the same command to compile the project on the build server (also windows 10 with VS 2017 Enterprise) gives several errors about the Fakes not existing. The exact errors look like this: XControllerTests.cs(10,20): error CS0234: The type or namespace 'Fakes' does not exist in the namespace 'System.Data.Common' (are you missing an assembly reference?) [C:\Runner\builds\xxx\XTests

I am using Visual Studio 2015 Enterprise RTM to write unit tests for a project that uses Unity Container . I have discovered that the simple act of adding a fakes assembly for Unity, not even actually using the fake, is sufficient to generate this exception: System.InvalidProgramException: Common Language Runtime detected an invalid program. Consider the following steps to reproduce: Using Visual Studio 2015 Enterprise RTM create a Unit Test project targeting .NET 4.6 Add the NuGet package "Unity" version 3.5.1404.0 Add the NuGet package "CommonServiceLocator" version 1.2.0 Write a single unit

I am trying to run this unit test using Microsoft Shims, but it throws me exception in Shims.Context.Create(); method. Environment: VS 2012, Win2K8 R2 namespace MyShimsUnitTest { [TestClass] public class MyUnitTest { [TestMethod] public void GetCurrentYear() { using (Microsoft.QualityTools.Testing.Fakes.ShimsContext.Create()) { // Some Logic... } } } } Detailed Exception: Result Message: Test method MyShimsUnitTest.MyUnitTest.GetCurrentYear threw exception: Microsoft.QualityTools.Testing.Fakes.UnitTestIsolation.UnitTestIsolationException: UnitTestIsolation instrumentation failed to initialize.

I'm using a simple proof-of-concept Fakes nUnit test: [Test] public void TestFakes() { using (var ctx = ShimsContext.Create()) { System.Fakes.ShimDateTime.NowGet = () => { return new DateTime(2000, 1, 1); }; Assert.That(DateTime.Now.Year, Is.EqualTo(2000)); } } This test runs in the Visual Studio Test Explorer, but doesn't run in: nUnit GUI nUnit console The JetBrains test runner (dotCover OR Resharper) TestDriven.net test runner In each of these, I receive the following error: Microsoft.QualityTools.Testing.Fakes.UnitTestIsolation.UnitTestIsolationException : Failed to resolve profiler path