![What does a test look like?[Test]public voidIsValid_Should_Return_True_When_Foo_Has_Name(){// Arrangevar foo = new Foo();foo.Name = "Charlie";// Actvar result = foo.IsValid;// AssertAssert.IsTrue(result);}](https://image.slidesharecdn.com/rc2010tdd-101215170709-phpapp01/85/Rc2010-tdd-6-320.jpg)
![What does a test look like?[Test]public voidIsValid_Should_Return_True_When_Foo_Has_Name(){// Arrangevar foo = new Foo();foo.Name = "Charlie";// Actvar result = foo.IsValid;// AssertAssert.IsTrue(result);}Unit of code we’re testingExpectations for our codeSingle assert, single outcome for test](https://image.slidesharecdn.com/rc2010tdd-101215170709-phpapp01/85/Rc2010-tdd-7-320.jpg)
Rc2010 tdd
- 1. Test Driven DevelopmentArrange, Act, Assert… AwesomeJason OffuttSoftware EngineerCentral Christian ChurchEmail: jason.offutt@cccev.comTwitter: @JasonOffutt #RefreshCache
- 2. What is TDD?It’s a development methodologyWrite automated test cases to define what your code should be doing
- 3. Write/Refactor code to satisfy test requirementsHow does it work?Write test case firstRun test (should fail)Write/Refactor code to satisfy test expectationsRun test again (should pass)???Profit
- 4. How does it work?To run these automated tests, we need a test framework.MS TestMicrosoft’s testing frameworkAble to run tests from within Visual Studio’s GUIComes out of the box with Visual Studio (Professional or higher)NUnitSimpler/Cleaner syntax than MS TestComes with it’s own client to run tests, just point it at an assemblyFree to download and use3rd party tools like ReSharper allow NUnit tests to be executed directly in Visual Studio
- 5. Test FirstThe goal is to write test cases to define expectations on how our code should behave.The result is that you end up with code that behaves in a predictable manner.In the end, you’ll have an entire suite of tests to prove your code works “correctly”.The first time we run a test, it should fail. We haven’t written any implementation to satisfy the test’s requirements yet.
- 6. What does a test look like?[Test]public voidIsValid_Should_Return_True_When_Foo_Has_Name(){// Arrangevar foo = new Foo();foo.Name = "Charlie";// Actvar result = foo.IsValid;// AssertAssert.IsTrue(result);}
- 7. What does a test look like?[Test]public voidIsValid_Should_Return_True_When_Foo_Has_Name(){// Arrangevar foo = new Foo();foo.Name = "Charlie";// Actvar result = foo.IsValid;// AssertAssert.IsTrue(result);}Unit of code we’re testingExpectations for our codeSingle assert, single outcome for test
- 8. Tips for writing good unit testsEach test should isolate a single unit of codeYou usually don’t want to have more than one or two asserts per test.
- 9. If you have several assertions in your tests, you are probably testing more than one thing, and could break it out into more than one test.Use “Arrange, Act, Assert” pattern to help keep your tests clean and simpleVerbose test method names can help you keep track of exactly what expectations you’re testing for
- 10. ImplementNow, we write the code to satisfy our test’s expectationspublic class Foo{public string Name { get; set; } public bool IsValid {get { return !string.IsNullOrEmpty(Name); } }}
- 11. Test AgainAfter implementing the test case’s requirements in our code, we run the test again.It should pass this time.Move on to the next test case.
- 12. Unit Tests vs Integration TestsIntegration Tests incorporate outside elements into testing (e.g. – databases, web services, etc).Unit Tests should be designed to completely isolate your code from everything else.Both are VERY valuable. If you can, do both.
- 13. Keeping Unit Tests CleanTo isolate our code, use Dependency Inversion to create a “seam” so we can inject a fake object.public classFooController{private readonlyIFooRepository repository;public FooController() : this(newArenaFooRepository()) { }public FooController(IFooRepository repository) {this.repository = repository; }}
- 14. Keeping Unit Tests CleanTo isolate our code, use Dependency Inversion to create a “seam” so we can inject a fake object.public interface IFooRepository{FooGetFooByID(int id);IEnumerable<Foo>GetFooList();void Create(Foofoo);void Delete(Foofoo);void Save();}
- 15. Keeping Unit Tests CleanTo isolate our code, use Dependency Inversion to create a “seam” so we can inject a fake object.// Called from test code// Pass fake repository class to simulate database// Implements IFooRepositoryvarcontroller = newFooController(newFakeFooRepository());// Called from production code// Default constructor uses ArenaFooRepository object that knows about Arena DBvar controller = newFooController();
- 16. Types of Fake ObjectsStubA simple fake object you could write by hand. Intended to fake a component (e.g. – act as a database/repository substitute).Intended to be very simple.MockOften generated by a framework like Rhino Mocks or Moq.More robust than Stubs in that they can track what pieces of code from the object they’re faking are being used.Suited well to faking more complex object structures (e.g. - HttpContext Request/Response).
- 17. But why go to all that trouble?This approach allows us to test our code more thoroughly. We can test application components and layers independently from each other.Test data access code (integration tests)Test entities/domain layer (unit tests)Test business/application logic layer (unit tests)
- 18. ResourcesNUnitRhino MocksMoqTacky cover = good book