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

Line 3: Line 3:
 
=== Questions to Answer for the Coach ===  
 
=== Questions to Answer for the Coach ===  
 
please send (via email) these answers ASAP to the coach...
 
please send (via email) these answers ASAP to the coach...
 +
 +
* what is your product? (e.g. self-driving car software, trading software, ...)
  
 
* programming language (and version)?
 
* programming language (and version)?

Revision as of 13:55, 2 December 2018



Questions to Answer for the Coach

please send (via email) these answers ASAP to the coach...

  • what is your product? (e.g. self-driving car software, trading software, ...)
  • programming language (and version)?
  • OS?
  • current IDE, if any?
  • current ATDD tool, if any?
  • current xUnit framework (e.g. JUnit), if any?
  • do most of the developers know basic VIM?


Setting

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


Software Tool Installs 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)


Computer Setup

  • first, see "tool installs" above
  • access to ALL the production legacy code


Supplies


Room

  • an unchanging room for the entire workshop
  • room with vast clear flat wall areas that will be covered in "wizard wall" plastic sheets
  • the tables will be set up in a U-shape around the screen