Environment - Team Based TDD exercise

Revision as of 12:00, 30 October 2011 by Clarman (talk | contribs) (New page: 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...)
(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 and network access are required, since the students are working in teams of 4, and doing continuos integration with a shared version control tool (e.g., subversion)


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


Software

For the team-based continuous integration work during TDD, each team of 4 people need shared access to a version control tool and shared repository, such as Subversion or Team Foundation Server.


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