Pair programming and introduction to TDD

Pair programming and introduction to TDD

• 1.
  Agenda • Goals ofthe session • Benefits • Preparation • Do’s • Introduction to TDD • Kata • Don’t do’s • Learning resources • Questions and Answers
• 2.
  Goals • Learning tocollaborate • Practice a technique for paired programming • Introduction to TDD • Retrospect on don’t do’s of paired programming
• 3.
  Why Paired Programming?
• 4.
  What would youneed? • Technique • Machine setup • Lots of patience and willingness to collaborate
• 5.
  Do’s • Let thepartner express idea fully • Be willing to try parter’s idea • Provide feedback during the participation • Code when its your turn • Show persistence and patience
• 6.
  TDD - TestDriven Development What Is TDD? • Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle. • TDD process defines codebase tests that drive what code you write
• 7.
  TDD - TestDriven Development How to TDD? Add test: before any code is written, an automated test is created that takes into account all the possible inputs, outputs and error conditions. Run test: the test is run for the first time. The test will fail because this is simply because no code yet exists to satisfy the test. Write code: the code is written, or improved to overcome any identified failings. This process can be repeated until the test is passed. Re-factor: once the test is passed, the code can be cleaned, or ‘re-factored’. As long as the code continues to pass the test, the code works. This allows the code to be improved while eliminating concerns that any changes might introduce bugs. Repeat: the whole process is repeated.
• 8.
  TDD - TestDriven Development
• 9.
  Why TDD? • Confidentabout meeting acceptance criteria • Writing the tests first requires you to really consider what do you want from the code. • TDD creates code that is maintainable, flexible, and easily extensible and there are fewer Bugs • The development time to market is shorter. • You are able to identify the errors and problems quickly. • TDD tells you whether your last change (or refactoring) broke previously working code. • TDD creates a detailed specification of the code
• 10.
  Unit Test andJUnit Framework A unit test is a piece of code written by a developer that executes a specific functionality in the code to be tested and asserts a certain behavior or state. A unit test targets a small unit of code, e.g., a method or a class. • assertTrue • AssertThat • AssertEquals
• 11.
  Pairing & TDDin action Watch Pairing and TDD in action - Check if a number is an even number - Session number nVCAwh
• 12.
  Pair and TDD FizzBuzzCoding Exercise: 1) If a number is a multiple of 3 write Fizz 2) If a number is a multiple of 5 write Buzz 3) If a number is a nultiple of 3 and 5 write FizzBuzz • To Do: 1. With your pair partner talk about the test scenarios 2. Write your first test 3. Pair partner writes code implementation
• 13.
  Lets practice • Goto your browser • http://cyber-dojo.org • Click on Join a session • Session id = mFAYuS •
• 14.
  Retrospective 1. What didyou learn from your partner? 2. What did you learn about yourself that you can improve upon next time?
• 15.
  Don’ts • Express yoursuperiority • Never back down • Watch silently • Code silently • Betray trust • Dominate keyboard • Win
• 16.
  Resources • Plural sightcourse - • Paired programming workshops by Bob Allen - Connect with us • Collaboration between team - https://it2.spt.ford.com/sites/SDM/FAF/Pages/R oles/ProductManagerOverview.aspx • Blog by Bob Allen - https://thehubat.ford.com/thread/14523