TDD with Visual Studio 2010
Download as PPTX, PDF1 like2,795 views
The document discusses test driven development (TDD) and how it can be used with Visual Studio 2010. It defines TDD as a process where developers write a failing test first, then code to pass the test, and refactor the code. The document outlines benefits of TDD like reduced bugs and defects, increased code flexibility, and easier addition of new features. It provides some advice on writing tests and using tools in Visual Studio 2010 like code coverage and contracts to help focus on TDD. Demo code is shown using unit testing and web testing in Visual Studio 2010.
![Test Driven DevelopmentTest-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle: the developer writes a failing automated test case that defines a desired improvement or new function (RED)produces code to pass that test (GREEN)finally refactors the new code to acceptable standards (REFACTOR)[Wikipedia]](https://image.slidesharecdn.com/20110125tddvisualstudio2010-110127131930-phpapp01/85/TDD-with-Visual-Studio-2010-2-320.jpg)
TDD with Visual Studio 2010
- 1. TDD: Test Driven Developmentwith Visual Studio 2010Stefano Paluellostefano.paluello@pastesoft.comhttp://stefanopaluello.wordpress.comTwitter: @palutz
- 2. Test Driven DevelopmentTest-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle: the developer writes a failing automated test case that defines a desired improvement or new function (RED)produces code to pass that test (GREEN)finally refactors the new code to acceptable standards (REFACTOR)[Wikipedia]
- 3. Test Driven DevelopmentTest Driven Development is one of the Extreme Programming principles (actually is the first one), but can be used also by itselfTDD is a CHANGE OF APPROACH for developers, is a new MINDSET, from writing code and then testing it (if there is enough time) to writing the test first and then writing the code to satisfy the test
- 4. Why do I need TDD?
- 5. Before TDD…The industry “standard” behavior was to write the code, and then write the tests. This leads to lots of applications without tests at allAlso the “good” applications with some tests written, weren’t (aren’t!!!) able to know whether the new code has broken the existing features
- 7. The new approach…Why do we have to stick on that plan?Kent Beck introduced a new method, inside his book about Extreme Programming (XP), in which he proposed to reverse this order by starting with unit tests and then writing the implementation.
- 8. Why TDD is good?Thinking about the tests pushes the developer to understand better the gathered requirementsWith the tests defined, the developer can focus on writing ONLY the code to satisfy them (reduce the over-engineered code, or dead-code)The unit tests help to check that any new modification won’t break the existing features
- 9. TDD is good (2)TDD speed-up your code! Ok, writing a whole set of code to test your program could appear as too much work, but with test you can trust your code more and you can have a quick feedback about your design and how your objects behave. When all tests have succeeded, you don’t need to spend so much time debugging the tested code.
- 10. TDD is notTest Driven Development is good, not God! Test Driven Development isn’t a magic stick that will solve ALL your problemsTest Driven Development is not working if there is not a REALLY mind shift
- 11. TDD != Unit Test Ok, this could be a bit confusing but…Test Driven Development is a process, is a mindset, a different approach, focusing on isolated test case to drive designUnit Test is a procedure, a part of the test process
- 12. How to justify TDD to PM Microsoft just published a research report where was pointed out that using TDD, the bugs and defects are reduced from 40% to 90% (nice code was made before! )http://research.microsoft.com/en-us/groups/ese/nagappan_tdd.pdf
- 13. How to justify TDD to Dev Team LeadTDD increase the software’s flexibilityTo be testable, a codebase using TDD is more decoupled and for this reason also adding more features is easier
- 14. How to justify TDD to…Stop thinking and justify!Just CODE!
- 15. Ops, some advices before code…Write simple test that verify only ONE behaviorAvoid dependencies between testsOne test class for every class within the production codeUse test initialization code before and test cleanup code after running your test (sealed context)Verify that all the tests are passed before move to another feature testMaximize the number of automated tests
- 16. TDD with Visual Studio
- 17. DemoUnit test with Visual Studio 2010
- 18. Demo RecapDespite the Intellisense, Visual Studio 2010 has some tools that help you to focus on TDDUsing Code Coverage, Visual Studio will show you the effectiveness of your tests
- 19. DemoWeb test with Visual Studio 2010
- 20. Some test “tools” for VS2010Code Contractsallow you to explicitly declare the preconditions, postconditions and invariant part of your codethis improves also the testing via runtime checking (injecting the contracts)it comes from Devlabs and it was an external assemblies for .Net 3.5, now included in .Net 4.0
- 21. VS2010 tools (2)Pex and MolesInside the Visual Studio 2010 Power tools extensionPex automatically generates test suites with high code coverage.Right from the Visual Studio code editor, Pex finds interesting input-output values of your methods (white box testing), which you can save as a small test suite with high code coverage. Microsoft Pex is a Visual Studio add-in for testing .NET Framework applications.Moles allows to replace any .NET method with a delegate. Moles supports unit testing by providing isolation by way of detours and stubs. The Moles framework is provided with Pex, or can be installed by itself as a Microsoft Visual Studio add-in (example test Asp.Net and Sharepoint applications!)
- 22. Contracts and Pex together
- 23. &Programmazione per Device:da Embedded a DesktopDomande & Risposte