Test driven development using Junit and MockIto
2 likes167 views
This document discusses test-driven development (TDD) using JUnit. It explains the philosophy of TDD, which is to write tests before writing code by beginning with the test in mind. The TDD process is then outlined as writing a test, running it and seeing it fail, stubbing the routine, running it again and seeing it fail, writing the code, and running it to see it pass. JUnit is introduced as a tool for TDD in Java that uses annotations to identify test methods. Mocking is also briefly discussed as allowing for better and faster testing by integrating different systems and simplifying designs to find bugs faster. Finally, the document suggests looking at a live example of how TDD can improve code
Test driven development using Junit and MockIto
- 3. What is
- 4. Philosophy of TDD: I believe that Stephen Covey would put it this way, “Begin with the test in mind” (This correlates to one of his 7 habits of Effective People, to wit, ”Begin with the end in mind”). One of the clear benefits is that the act of designing a test (for a requirement, for an interface, for any object or system of objects) provokes us to focus sooner on the details of the desired outcomes. Thus,TDD can accelerate the emergence of a design, and theTDD purists would have us write the tests first before we code the implementations. It helps us clarify our goals, and develop assessment criteria, so we can agree—in advance—on what will be the measures of success.
- 5. Test Driven Development • Write a test • Run the test – it fails to compile because the called routine hasn’t been written • Stub the routine • Run the test – it fails because the stub doesn’t do anything yet • Write the routine for the body of stub • Run the test – it passes (hopefully) • Repeat until complete
- 6. Life Cycle
- 7. What is JUnit A tool for test-driven development. History : Kent Beck and Gamma (of design patterns Gang of Four) developed JUnit on a flight from Zurich toWashington, D.C. Junit has become the standard tool forTest- Driven Development in Java (seeJunit.org). Junit test generators now part of many Java IDEs (Eclipse, BlueJ, Jbuilder, DrJava).
- 11. Why Mock ? Better and FastTesting Integrate different Systems Simpler Small box >> Better Design Faster to find Bugs Why bother asking ?
- 13. Mockito is a mocking framework that tastes really good.It lets you write beautiful tests with clean & simple API. Mockito doesn't give you hangover because the tests are very readable.
- 14. Time to minimize the PPT and See the Live Example : HowTest Driven Development can Help us to improve Quality of Code for our Applications...OMNI/NSCC
- 16. ThankYou
Editor's Notes
- #2: Test Driven Development With JUnit <number>
- #3: <number> Contact information – I’m Devender Singh Garha on facebook and Devender Singh Garha on linkedin and most of the other social networking sites out there. If you don’t take any other notes – get my email address down because you can take the slides home but you can’t take me home… Unless you’ve got really good Scotch.
- #4: The first question that we have to answer is “What is T.D.D. ?” <number>
- #5: Philosophy of TDD:I believe that Stephen Covey would put it this way, “Begin with the test in mind.” (This correlates to one of his 7 Habits of Effective People, to wit, “Begin with the end in mind.”) One of the clear benefits is that the act of designing a test (for a requirement, for an interface, for any object or system of objects) provokes us to focus sooner on the details of the desired outcomes. Thus, TDD can accelerate the emergence of a design, and the TDD purists would have us write the tests first before we code the implementations. It helps us clarify our goals, and develop assessment criteria, so we can agree—in advance—on what will be the measures of success. <number>
- #6: And then if you go to Wikipedia (the compendium of all human knowledge), they define Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle: first the developer writes an (initially failing) automated test case that defines a desired improvement or new function, then produces the minimum amount of code to pass that test, and finally refactors the new code to acceptable standards. Kent Beck, who is credited with having developed or 'rediscovered' the technique, stated in 2003 that TDD encourages simple designs and inspires confidence. <number>
- #7: \ <number>
- #8: A tool for test-driven development. History : Kent Beck and Gamma (of design patterns Gang of Four) developed JUnit on a flight from Zurich to Washington, D.C. Junit has become the standard tool for Test-Driven Development in Java (see Junit.org). Junit test generators now part of many Java IDEs (Eclipse, BlueJ, Jbuilder, DrJava). <number>
- #9: <number>
- #13: <number>
- #14: Mockito is a mocking framework that tastes really good.It lets you write beautiful tests with clean & simple API. Mockito doesn't give you hangover because the tests are very readable. <number>
- #16: <number>
- #18: <number>