Download to read offline
Uploaded bydasdom
Tdd
The document discusses test-driven development (TDD) with Swift. It outlines the rules of TDD, which state that code can only be written to pass a failing unit test and no more production code than needed. The red-green-refactor process is also summarized, where a failing test is written, then code to pass it, then refactoring. Benefits of unit testing like fast feedback, catching edge cases, and preventing regressions are listed. Advantages of TDD like automatic testability, modularity, coverage and living documentation are provided. Some drawbacks like initial slower speed and learning curve are also noted.
![Getting Started with Apache Spark: Big Data Made Simple [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/apachesparkgettingstarted-260203175547-8361bcc3-thumbnail.jpg?width=640&height=640&fit=bounds)
Tdd
- 1. SwiftConf.com Dominik Hauser Test-Driven iOSDevelopment with Swift
- 2. SwiftConf.com You are notallowed to write any production code unless it is to pass a failing unit test You are not allowed to write any more of a unit test than is sufficient to fail; and compilation failures are failures You are not allowed to write any more production code than is sufficient to pass the one failing unit test The Rules (Uncle Bob)
- 3. SwiftConf.com Red: Write afailing test Green: Write the simplest code that makes the test pass Refactor: Improve the code without breaking the tests Red, Green, Refactor
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10. SwiftConf.com Automatic testability Automatic modularity Hightest coverage Refactoring Living documentation Why TDD?
- 11. SwiftConf.com No silver bullet Slowerat first Training curve Keep in mind
- 12.