Introduction to Test Driven Development
- 1. “TDD - Clean code that works -Ron Jeffries
- 2. WHAT IS TDD ➤ Test is written firstly ➤ Code is not considered finished till all tests passed ➤ All requirement are covered in tests
- 3. HOW TO PERFORM TDD ADD/AMEND TEST The test must fail Write some code, MAKE IT WORK Run all tests, ensure them all succeed Refactor the code, MAKE IT RIGHT
- 4. WHY TDD ➤ Safe modification ➤ Mistakes are shallow and obvious ➤ Self-documenting code: the test! ➤ Solid design before code writing ➤ Shorten cycle of code writing and testing ➤ Code is decoupled
- 5. WHAT CONCERNS YOU? ➤ Requirements must be understood fully before hand ➤ TDD vs exploratory development ➤ Coding and testing not in parallel
- 6. “BDD is a second-generation, outside-in, pull- based, multiple-stakeholder, multiple-scale, high- automation, agile methodology. It describes a cycle of interactions with well-defined outputs, resulting in the delivery of working, tested software that matters. -Dan North
- 7. WHAT IS BDD ➤ Behavior-Driven Development, or BDD is an Agile software technique that encourages collaboration between developers and non- technical or business participants in a software project ➤ Build clear understanding of desired behaviour through discussion with stakeholders ➤ Test cases in a natural language
- 8. HOW TO PERFORM BDD ➤ A user story’s behaviour can be defined by acceptance criteria. In this pattern ➤ GIVEN some initial context, ➤ WHEN an event occurs, ➤ THEN ensure an outcome
- 9. TOOL SET IN BDD ➤ Dozens of frame work available ➤ Cucumber (Ruby) ➤ Lettuce (Python) ➤ Rspec (Ruby) ➤ Gherkin language