Jdojo@Gbg Introduction
Upcoming SlideShare
Loading in...5

Jdojo@Gbg Introduction



Slides used at the first startup meeting of a series of coding dojo sessions, focusing on TDD mostly (Meetup group JDojo@Gbg)

Slides used at the first startup meeting of a series of coding dojo sessions, focusing on TDD mostly (Meetup group JDojo@Gbg)



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Jdojo@Gbg Introduction Jdojo@Gbg Introduction Presentation Transcript

  • JDojojsolutions.se
  • Bugs
  • The Problem● Bugs are costly● Fixing bugs reported from testers costs even more● Fixing bugs reported from en users costs even more than "even more"
  • What solution?
  • IBM & Microsoft Report ● 40 - 90% fewer bugs discovered during testing ● 15 - 35% more time spent on development
  • TDD vs Traditional TestingDoesnt remove theneed for regular,traditional testing:● Exploratory testing● QA testing● User Interface testing● Performance testing● ...
  • Test-Driven Developmemt Kent Beck on TDD: Im not a great programmer, Im just a good programmer with great habits.
  • Red, Green, Refactor ● Write a test, get it to compile, get a red bar ● Quickly make the test pass, get a green bar ● Refactor, "clean code", run tests frequently - the "bar" should stay green
  • Another Take ● write test first ● write smallest possible implementation ● clean up ➔ no "dead" code - its all covered ➔ nice API - designed outside in
  • Baby Steps● as small as possible● as large as is comfortable ● experience of TDD ● technology knowledge ● boldness ● understanding of the problem domain
  • 3A ● Arrange ● Act ● Assert
  • Benefits ● More confident ● More productive ● More reliable ● More agile
  • Drawbacks● More code to maintain● Takes longer● Easy to learn, but harder to master
  • JDojo@Gbg A safe environment to learn coding skills such as Test-driven Development and writing clean code
  • Dave Thomas - Kata"Pragmatic Dave":A kata is an exercise inkarate where you repeata form many, manytimes, making littleimprovements in each.
  • The Coders Dojo Concept presented at XP 2005 byLaurent Bossavi and Emmanuel Gaillot
  • Coding Dojo ● A moderator presents a kata ● Solve the kata, and ... ● Learn from others, teach what you know ● Short retrospective
  • Kata ● Small programming exercise - 1-2 hours ● Start from scratch ● Strictly test-driven ● Next time, start over and try new approach ● Practice until you master the kata
  • Dojo Rules● Dont criticize until we have a green bar● Strict usage of TDD● Everyones obligation to point out any non- TDD behaviour
  • JDojo@GbgFredrik Wendt jsolutions.se
  • All vector art comes from Gnome base icon set, which is licensed under LGPL. download.gnome.org/sources/gnome-icon-theme Man on vacuum cleaner from tpp-bloggen. Firebug logotype from getfirebug.com Baby Steps photo from seandreilinger at flickr.com Picture of Dave Thomas from x180 at flickr.com Picture of Kent Beck from Three Rivers Institute web site