The document discusses the importance and methodology of unit testing in software development, emphasizing quick feedback, regression prevention, and control of code. It outlines best practices for writing effective tests, including clarity, simplicity, and the importance of readability. The document also lists various tools and frameworks available for unit testing.

1. Real life unit testingDror Helper

2. Who am I?Software DeveloperPart time blogger http://blog.drorhelper.com/@dhelperOne thing was the same wherever I worked…

3. AgendaUnit tests - what, how and whyTools of the tradeHow to write better testsWriting tests when it’s hard to test

4. Sounds familiar?Every ten bugs I fix I create a new one…I have no idea what caused that issue…I’d rather not change that function…It is impossible to unit test our project!Setting my test environment takes too long

5. Avoid stupid bugs

6. Unit testsUnit TestsTest specific functionalityClear pass/fail criteriaGood unit test runs in isolation

7. What is a Unit TestUnit tests[TestMethod]public void CheckPassword_ValidUser_ReturnTrue(){bool result = CheckPassword(“user”, “pass”);Assert.IsTrue(result);}

8. What is a Unit TestUnit tests[Test]public void CheckPassword_ValidUser_ReturnTrue(){bool result = CheckPassword(“user”, “pass”);Assert.That(result, Is.True);}

9. The kind of testUnit tests should be:SmallAtomicTest a single functional unitIsolated!Integration tests are used to test system wide functionalityUnit tests

10. Why use automated unit tests?Quick feedbackRegressionGain control of your codeUnit tests

11. Avoid stupid bugsUnit tests

12. Tools of the tradeToolsServerSource ControlBuild ServerBuild ScriptDev MachineTest RunnerUnit Testing FrameworkIsolation FrameworkCode Coverage

13. Continuous IntegrationToolsWhat’s new?CommitBuild Server(TeamCity)There you goStart workingBuild artifactsWe automatically gotError reports & logs

14. New version installer

15. Help files

16. More…Source Control(SVN)Build Agents(FinalBuilder)

17. Build Script at a GlanceTools

18. TeamCity at a GlanceTools

19. Development environmentMake it easy to write and run testsUnit test frameworkTest RunnerIsolation frameworkKnow where you standCode coverage Tools

20. Unit testing frameworksNUnitxUnitMSTestGallio (MbUnit)NBehaveList of unit testing frameworks: http://en.wikipedia.org/wiki/List_of_unit_testing_frameworksTools

21. Test RunnersToolsVisual Studio (MSTest)

22. TestDrive.Net

23. R# TestRunner

24. CodeRushTestRunner

25. NUnitItHow to write better testsWrite better testsWrite easy to understand testsReuse code where appropriateRunning test should be easyAvoid fragile testsTrust Your Tests!

26. Readability is importantWhy did the test fail?Avoid unnecessary debuggingUnderstand what the test does!Write better tests

27. Easy to understand unit testsNames are importantDon’t be afraid to repeat yourselfArrange-Act-AssertOr Act-Assert-ArrangeWrite better tests

28. Write readable testsTest only one thing (most of the time)KISS – avoid logic in your testWrite better tests

29. Duplicate code problemWrite better testsAfter refactoring I need to re-write my tests.Writing the same code twice is wrong

30. Reuse codeCreate objects using factoriesManipulate and configure initial stateRun common tests in common methods Write better tests

31. Just remember Readability is important - It’s still ok to repeat yourselfWrite better tests

32. Easy to run Running the tests takes too longSetting complicated testing environmentWrite better tests