Environment - Minor TDD exercise

Revision as of 09:21, 17 October 2011 by Clarman (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Computers are used occasionally throughout the course.

However, we only need (and want) 1 computer for each 2 students; e.g., if 16 students, then 8 computers. Often, it is possible for students to bring their own laptop.

Internet access is a "very nice to have" but we can live without it if difficult to achieve.

Power strips and extension cords are generally needed in order to supply power to the computers safely.


For acceptance TDD (ATDD), we will *probably* be using Robot Framework or Fit/Fitnesse, but in some versions of the course, we use the same tool as for unit TDD (e.g., JUnit for acceptance and unit TDD).

ACTION >> check with the coach for the choice of ATDD tool. After checking with the coach on which ATDD tool, then please install it.

If Robot Framework, including all the JYTHON elements: http://code.google.com/p/robotframework/ (The "one click installer" approach for Robot Framework is best. Also, TEST that it is working after installation).

If Java group:

  • latest PUBLIC (not internal to your company) version of Java Runtime (JRE)
  • latest PUBLIC (not internal to your company) version of Eclipse or NetBeans

If C++ group:

  • normally, we do the exercises in Java anyway, to avoid burning hours on awkward/slow tool setup and use in C++); Java is similar to C++, and sufficient for the educational goals (of introducing the idea of TDD and refactoring). However, if the client is really keen on doing the exercises in C++, this is possible (the coach is skilled in C++). Action >> 1+ weeks before the course, please let the coach know if C++ is important.

If .NET group:

  • Visual Studio in C#

If C group:

  • usually, Eclipse with CDT and the GNU tool chain (or cygwin or MinGW variant) -- ask the coach