Using EF's POCO Features for Unit Testing

Using Entity Framework's New POCO Features: Part 2 (Unit Testing) Presented by Jamie Phillips http://devblog.petrellyn.com

Who is Jamie Phillips ,[object Object],[object Object],[object Object]

Unit Testing or Integration Testing? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

The Restaurant Analogy: Unit versus Integration Tests (Roy Osherove)

It is not a Unit Test if: ,[object Object],[object Object],[object Object],[object Object],[object Object]

How can true unit testing be achieved? ,[object Object],[object Object],[object Object]

What is Dependency Injection (DI)? ,[object Object],[object Object],[object Object]

Types of Dependency Injection ,[object Object],[object Object],public class Manager { IEFWorkshopContext _context; public Manager( ) { _context = new EFWorkshopContext(); } public IEFWorkshopContext Context { get { _context = value ; } } }

Types of Dependency Injection (cont) ,[object Object],[object Object],[object Object],public class Manager { IEFWorkshopContext _context; public Manager( ) { _context = new EFWorkshopContext(); } public Manager( IEFWorkshopContext i_context) { _context = i_context; } }

DI is only one half of the equation ,[object Object],[object Object],[object Object]

What is Mocking? ,[object Object],[object Object],[object Object],[object Object],[object Object]

How does this all fit in with EF? ,[object Object],[object Object]

How does this fit together? ,[object Object],[object Object],[object Object]

Now what? Identify Dependencies ,[object Object],public interface IEFWorkshopContext { IObjectSet<Address> Addresses { get; } IObjectSet<Beer> Beers { get; } IObjectSet<Brewery> Breweries { get; } IObjectSet<SalesPerson> SalesPeople { get; } IObjectSet<Person> People { get; } IObjectSet<FavoriteBeer> FavoriteBeers { get; } IObjectSet<Customer> Customers { get; } IObjectSet<CustomerType> CustomerTypes { get; } }

Now what? Create Default Class ,[object Object],public class EFWorkshopContext : ObjectContext, IEFWorkshopContext { /// <summary> /// Initializes a new EFWorkshopEntities object using the /// connection string found in the 'EFWorkshopEntities' /// section of the application configuration file. /// </summary> public EFWorkshopContext() : base( "name=EFWorkshopEntities", "EFWorkshopEntities") { } ...

Now what? Create IObjectSet<T> Properties ,[object Object],private IObjectSet<Address> _Addresses; public IObjectSet<Address> Addresses { get { return _Addresses ?? (_Addresses = CreateObjectSet< Address>()); } }

Now what? Create Manager Class ,[object Object],public class Manager { IEFWorkshopContext _context; public Manager() { Initialize(null); } internal Manager( IEFWorkshopContext i_context) { Initialize(i_context); } private void Initialize( IEFWorkshopContext i_context) { _context = i_context ?? new EFWorkshopContext(); }

Now what? Prepare for mocks ,[object Object],public static class ObjectSetExtension { public static IObjectSet<T> AsObjectSet<T>( this List<T> entities) where T : class { return new MockObjectSet<T>(entities); } }

Now what? Writing the Test Method - Arrange ,[object Object],[object Object],// - ARRANGE - // Create the stub instance IEFWorkshopContext context = MockRepository .GenerateStub <IEFWorkshopContext>(); // Create the out-of-range id int id = -1; // declare instance that we want to "retrieve" Person person; // Create a real instance of the Manager Manager manager = new Manager(context); // declare the expected Exception Exception expectedExc = null;

Now what? Writing the Test Method - Act ,[object Object],// - ACT - try { person = manager.GetPerson(id); } catch ( Exception exc) { expectedExc = exc; }

Now what? Writing the Test Method - Assert ,[object Object],// - ASSERT - // Make absolutely sure that the expected exception type was thrown Assert .IsNotNull(expectedExc); Assert .IsInstanceOfType(expectedExc, typeof ( ArgumentException )); Assert .IsInstanceOfType(expectedExc, typeof ( ArgumentOutOfRangeException )); // Make sure that the method was NOT called. context.AssertWasNotCalled(stub => { var temp = stub.People; });

Putting it together... ,[object Object]

Code Coverage ,[object Object],[object Object],[object Object],[object Object]

Demonstration on Code Coverage

DI oh my! ,[object Object],[object Object],[object Object],[object Object]

ADDITIONAL MATERIAL ,[object Object]

Which Unit Testing frameworks? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

What Mocking frameworks are available for .NET? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Comparison between RhinoMock, Moq, NMock2 and TypeMock Ease of use Cost Likes Dislikes Rhino Mocks Easy due to being strongly-typed, which makes the syntax great and "safe". Free Strongly typed instancing - no need to use string references. Full AAA support Record / Replay should be implied not expected. Moq Doesn’t use record / replay scenarios! similar to Rhino Mocks Free Similar to Rhino Mocks, with no support for record / replay Creates wrapper of mock instance. NMock Use of strings to call property methods / normal methods. Free Pales to insignificance in contrast to RhinoMocks, Moq or TypeMock Need to use string declarations for instancing. Type Mock Extremely easy to implement mocking because it uses the .NET framework profiler API to monitor an application's execution. Expensive The fact that it "plugs-in" to the CLR and captures type references, means that no code changes need to be done on legacy components. Prohibitively Expensive.

Using EF's POCO Features for Unit Testing

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Using EF's POCO Features for Unit Testing

Semelhante a Using EF's POCO Features for Unit Testing (20)

Último

Último (20)

Using EF's POCO Features for Unit Testing

Notas do Editor