Downloaded 12 times
Uploaded byGamal Shaban
Test Driven Development Part 1
The document discusses Test Driven Development (TDD), detailing its benefits such as improved code quality and reduced costs of change. It outlines the steps involved in TDD, emphasizing the red-green-refactor cycle for writing tests, coding, and refactoring. The presentation is part of a session intended to educate about TDD within the context of mobile applications and software development.
More Related Content
Similar to Test Driven Development Part 1
Test Driven Development Part 1
- 1. Test Driven DevelopmentTestDriven Development Part 1 Gamal ShaabanGamal Shaaban International Centers Orange Labs Cairo Mobile Applications & Software Development
- 2.
- 3.
- 4. 4 Orange restricted Session-1Session-1 4 •Why TDD • Quality In Time and Cost • Cost To Change • Steps To TDD • Red Green Refactor Cycle • Write Red Test • Write Green Code • Do Refactoring Code
- 5. 5 Orange restricted WhyTDD: Quality TriangleWhy TDD: Quality Triangle • TDD benefits o Clean Design o Fast Feedback o Concrete Evidence That Your Software Works o Write Better Code o Reduced Gold-Plating o Regression Test Suite 5
- 6. 6 Orange restricted CostTo Change ChartCost To Change Chart http://www.agilemodeling.com/essays/costOfChange.htm 6
- 7. 7 Orange restricted StepsTo TDDSteps To TDD 7
- 8. 8 Orange restricted RedGreen RefactorRed Green Refactor CycleCycle
- 9. 9 Orange restricted Writefail tests, make test passes, refactor your code, repeat this action 9
- 10. 10 Orange restricted HowTo Do TDDHow To Do TDD 1. Analyze the requirements and write the list of tasks or features 2. Pick a task or feature 3. Brainstorm a list of tests for the task or feature 4. Review the tests list and pick a test 5. Write the test case 6. Run the test case and see it fails to compile 7. Write only enough code that the test case compiles 8. Run the test and see running the code fails 9. Write only enough code to just pass the test 10.Refactor the production code and eliminate duplication 11.Repeat 10
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
Editor's Notes
- #4 “TDD Intro” Is all code guilty until proven innocent??? can we find out?
- #5 why tdd: 30 min Steps to TDD: 90 min Workshop for doing red green test: 120 min
- #9 write Red test. write greed code that passes the test. refactor your code.
- #13 Make a workshop for writing a test first then code example write red test. write greet code do the cycle again. do fibonacci example.