Environment - Team Based TDD exercise - Revision history

Clarman: /* Software */

2013-10-07T18:28:57Z

Software

Clarman: /* Software */

2013-10-07T16:52:34Z

Software

Clarman at 16:51, 7 October 2013

2013-10-07T16:51:44Z

Clarman: /* Software */

2013-10-07T16:51:29Z

Software

Clarman at 16:49, 7 October 2013

2013-10-07T16:49:26Z

Clarman at 13:02, 26 April 2013

2013-04-26T13:02:16Z

Clarman at 13:01, 26 April 2013

2013-04-26T13:01:40Z

Clarman: /* Software */

2012-12-09T18:58:54Z

Software

Clarman at 18:56, 9 December 2012

2012-12-09T18:56:01Z

Clarman: 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...

2011-10-30T19:00:29Z

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...

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 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

@@ Line 19: / Line 19: @@
 For Acceptance TDD, an ATDD tool, such as
-* Fitnesse at http://fitnesse.org/
+* Fitnesse (server side setup) at http://fitnesse.org/
 * Robot Framework at http://robotframework.org/

← Older revision		Revision as of 16:52, 7 October 2013
Line 15:		Line 15:


−	On the other hand, if only working in pairs (and not larger teams), then no version control tool or repository is needed. the non-team-based course version is most common for ~~public~~ courses ~~with heterogeneous attendees~~.	+	On the other hand, if only working in pairs (and not larger teams), then no version control tool or repository is needed. the non-team-based course version is most common for short courses (such as the TDD course).

@@ Line 21: / Line 21: @@
 * Fitnesse at http://fitnesse.org/
 * Robot Framework at http://robotframework.org/
 If Java group:

← Older revision		Revision as of 16:51, 7 October 2013
Line 17:		Line 17:
	On the other hand, if only working in pairs (and not larger teams), then no version control tool or repository is needed. the non-team-based course version is most common for public courses with heterogeneous attendees.		On the other hand, if only working in pairs (and not larger teams), then no version control tool or repository is needed. the non-team-based course version is most common for public courses with heterogeneous attendees.

		+
		+	For Acceptance TDD, an ATDD tool, such as
		+	* Fitnesse at http://fitnesse.org/
		+	* Robot Framework at http://robotframework.org/

	If Java group:		If Java group:

@@ Line 5: / Line 5: @@
-Internet access and network access are required, since the students are working in teams of 4, and doing continuous integration with a shared version control tool (e.g., subversion)
+Internet access and network access are required, since the students are working in teams of 4 or more, and doing continuous integration with a shared version control tool (e.g., subversion)
@@ Line 12: / Line 12: @@
 == Software ==
-If we are doing teams-of-4 team-based development, then 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. the team-based course version is most common for internal 1-company courses.
+If we are doing team-based development, then for the team-based continuous integration work during TDD, each team people need shared access to a version control tool and shared repository, such as Subversion. the team-based course version is most common for longer courses such as ''Agile Software Development'', or for internal 1-company courses.

@@ Line 19: / Line 19: @@
 If Java group:
-* (most common choice) latest PUBLIC (not internal to your company) version of Java Runtime (JRE)
+* latest PUBLIC (not internal to your company) version of Java Runtime (JRE)
-* OR... latest PUBLIC (not internal to your company) version of Eclipse or NetBeans
+* latest PUBLIC (not internal to your company) version of Eclipse (most common choice) or NetBeans (less common choice)

← Older revision		Revision as of 18:58, 9 December 2012
Line 12:		Line 12:

	== Software ==		== 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 we are doing teams-of-4 team-based development, then 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. the team-based course version is most common for internal 1-company courses.
		+
		+
		+	On the other hand, if only working in pairs (and not larger teams), then no version control tool or repository is needed. the non-team-based course version is most common for public courses with heterogeneous attendees.

← Older revision		Revision as of 18:56, 9 December 2012
Line 5:		Line 5:


−	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)	+	Internet access and network access are required, since the students are working in teams of 4, and doing continuous integration with a shared version control tool (e.g., subversion)