<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bas de Ruiter</title>
    <description/>
    <link>https://speakerdeck.com/winkbrace</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/winkbrace.rss"/>
    <lastBuildDate>2016-12-16 10:33:02 -0500</lastBuildDate>
    <item>
      <title>Practical TDD</title>
      <description>Test Driven Development. A given for many software engineers, but a lot of php developers are still only prodding at it with a stick from a safe distance. 

This talk won't be an introduction to TDD. I'm gonna try to take away this fear by giving opinionated answers to the Difficult Questions. I hope it will lead to some good discussions at the end. 

1. What is the purpose of TDD?  
2. What are the pitfalls of TDD? 
3. How do I TDD with the database? 
4. How do I TDD with web services? 
5. How do I TDD with the front end? 
6. How do I stick to TDD when the deadline is approaching? 
7. How much code coverage should we aim for? 
8. How long may a test suite run? 
9. How can I start with TDD in a legacy code base? 
10. How to convince my boss TDD is good? 

Speaker: Bas de Ruiter

Bas is software architect at Harver. He's been an Oracle and later PHP developer for about 12 years. Besides his enthusiasm for domain driven design, he is a big fan of test driven development. He has set it up and used it for all projects he has worked on in the past five years.</description>
      <media:content url="https://files.speakerdeck.com/presentations/8fc4d12cfc864987adc3910dc3f758af/preview_slide_0.jpg?7368943" type="image/jpeg" medium="image"/>
      <content:encoded>Test Driven Development. A given for many software engineers, but a lot of php developers are still only prodding at it with a stick from a safe distance. 

This talk won't be an introduction to TDD. I'm gonna try to take away this fear by giving opinionated answers to the Difficult Questions. I hope it will lead to some good discussions at the end. 

1. What is the purpose of TDD?  
2. What are the pitfalls of TDD? 
3. How do I TDD with the database? 
4. How do I TDD with web services? 
5. How do I TDD with the front end? 
6. How do I stick to TDD when the deadline is approaching? 
7. How much code coverage should we aim for? 
8. How long may a test suite run? 
9. How can I start with TDD in a legacy code base? 
10. How to convince my boss TDD is good? 

Speaker: Bas de Ruiter

Bas is software architect at Harver. He's been an Oracle and later PHP developer for about 12 years. Besides his enthusiasm for domain driven design, he is a big fan of test driven development. He has set it up and used it for all projects he has worked on in the past five years.</content:encoded>
      <pubDate>Thu, 15 Dec 2016 00:00:00 -0500</pubDate>
      <link>https://speakerdeck.com/winkbrace/practical-tdd</link>
      <guid>https://speakerdeck.com/winkbrace/practical-tdd</guid>
    </item>
  </channel>
</rss>
