Difference between revisions of "Workshop Environment - SBE ATDD UTDD with mob-programming"

Line 1: Line 1:
 +
<br>
 +
<br>
 
=== Setting ===  
 
=== Setting ===  
 
people around a projector and screen. 1 computer. mob programming on production code.
 
people around a projector and screen. 1 computer. mob programming on production code.
Line 4: Line 6:
  
 
=== Preparation before the workshop ===  
 
=== Preparation before the workshop ===  
* install and connect Fitnesse -- or another agreed ATDD tool -- to your system under development, so that we can call upon public APIs of your system, via a Fitnesse Fixture.
+
* install and connect Fitnesse (an ATDD tool) to your system under development, so that we can call upon public APIs of your system, via a Fitnesse Fixture.
  
 
* complete full "connect the dots" *before* the workshop, proving that Fitnesse is connected and can make calls
 
* complete full "connect the dots" *before* the workshop, proving that Fitnesse is connected and can make calls
  
 +
* CHECK IDE CHOICE WITH COACH, and then install the chosen IDE with built-in refactoring
  
=== Participants ===
+
* install and check an xUnit TDD tool, such as JUnit (if not already integrated with the IDE)
* either 1 existing stable team, or a new mixed group of developers from diverse technologies of relevance
 
  
  

Revision as of 13:18, 2 December 2018



Setting

people around a projector and screen. 1 computer. mob programming on production code.


Preparation before the workshop

  • install and connect Fitnesse (an ATDD tool) to your system under development, so that we can call upon public APIs of your system, via a Fitnesse Fixture.
  • complete full "connect the dots" *before* the workshop, proving that Fitnesse is connected and can make calls
  • CHECK IDE CHOICE WITH COACH, and then install the chosen IDE with built-in refactoring
  • install and check an xUnit TDD tool, such as JUnit (if not already integrated with the IDE)


Supplies

  • computer
  • projector
  • screen
  • chairs
  • table
  • black whiteboard markers
  • paper towel for erasing
  • vast clear wall areas covered in "wizard wall" (etc) sheets, for whiteboarding floor-to-ceiling
  • access to the production code