Unit Test Tutorial 1 - Revision history

Jedbox: /* Link to Tutorial Part 2 */

2010-05-25T06:04:40Z

‎Link to Tutorial Part 2

2010-05-24T14:36:33Z

2010-05-24T14:35:14Z

2010-05-24T02:53:52Z

‎Add to category Testing

2010-05-24T02:49:11Z

‎How a Unit Test should NOT be written

2010-05-24T02:40:35Z

‎Add new Chapter

2010-04-19T02:44:24Z

‎Running Tests

2010-04-19T02:43:44Z

‎Running Tests

2010-04-19T02:40:15Z

‎3. Tests assertions about the results (outputs)

2010-04-19T02:39:02Z

‎3. Tests assertions about the results (outputs)

@@ Line 216: / Line 216: @@
 Unexperienced users often tap into pitfalls when writing unit test testcases.
 A good tutorial on how to avoid these pitfalls, sometimes also called anti-patterns, is summarized at [http://exubero.com/junit/antipatterns.html].
 [[Category:Bug Squad]] [[Category:Development]] [[Category:Testing]] [[Category:Automated Testing]]

← Older revision		Revision as of 14:36, 24 May 2010
Line 218:		Line 218:


−	[[Category:Testing]][[Category:Automated Testing]]	+	[[Category:Bug Squad]] [[Category:Development]] [[Category:Testing]] [[Category:Automated Testing]]

← Older revision		Revision as of 14:35, 24 May 2010
Line 1:		Line 1:
−
	= Unit Testing and Joomla! =		= Unit Testing and Joomla! =

Line 219:		Line 218:


−	[[Category:Testing]]	+	[[Category:Testing]][[Category:Automated Testing]]

← Older revision		Revision as of 02:53, 24 May 2010
Line 217:		Line 217:
	Unexperienced users often tap into pitfalls when writing unit test testcases.		Unexperienced users often tap into pitfalls when writing unit test testcases.
	A good tutorial on how to avoid these pitfalls, sometimes also called anti-patterns, is summarized at [http://exubero.com/junit/antipatterns.html].		A good tutorial on how to avoid these pitfalls, sometimes also called anti-patterns, is summarized at [http://exubero.com/junit/antipatterns.html].
		+
		+
		+	[[Category:Testing]]

← Older revision		Revision as of 02:49, 24 May 2010
Line 214:		Line 214:

	== How a Unit Test should NOT be written ==		== How a Unit Test should NOT be written ==
		+
		+	Unexperienced users often tap into pitfalls when writing unit test testcases.
		+	A good tutorial on how to avoid these pitfalls, sometimes also called anti-patterns, is summarized at [http://exubero.com/junit/antipatterns.html].

← Older revision		Revision as of 02:40, 24 May 2010
Line 212:		Line 212:
	}		}
	</source>		</source>
		+
		+	== How a Unit Test should NOT be written ==

@@ Line 118: / Line 118: @@
 </pre>
-There are many situations where you may not want to run the whole test suite.  See the [Running Unit Tests] page for details on how to be selective with the tests that you run.
+There are many situations where you may not want to run the whole test suite.  See the [[Running Unit Tests]] page for details on how to be selective with the tests that you run.
 == Anatomy of a Test ==

← Older revision		Revision as of 02:43, 19 April 2010
Line 118:		Line 118:
	</pre>		</pre>

		+	There are many situations where you may not want to run the whole test suite. See the [Running Unit Tests] page for details on how to be selective with the tests that you run.

	== Anatomy of a Test ==		== Anatomy of a Test ==

@@ Line 199: / Line 199: @@
+		)
 	);
 	$result_array = JArrayHelper::getColumn($test_array, 'country');
 	$this->assertThat(
 		$result_array,

@@ Line 180: / Line 180: @@
 Our final test looks like:
 <source lang="php">
-	public function testGetColumnTutorial()
+public function testGetColumnTutorial()
-−
+{
-		$test_array = array(
+	$test_array = array(
-			array(
+		array(
-				'sport' => 'football',
+			'sport' => 'football',
-				'teams' => '16',
+			'teams' => '16',
-				'country' => 'United States'
+			'country' => 'United States'
-			),
+		),
-			array(
+		array(
-				'sport' => 'badminton',
+			'sport' => 'badminton',
-				'teams' => '12',
+			'teams' => '12',
-				'country' => 'Germany'
+			'country' => 'Germany'
-			),
+		),
-			array(
+		array(
-				'sport' => 'basketball',
+			'sport' => 'basketball',
-				'teams' => '20',
+			'teams' => '20',
-				'country' => 'Canada'
+			'country' => 'Canada'
-−
+		)
-		);
+	);
-		$result_array = JArrayHelper::getColumn($test_array, 'country');
+	$result_array = JArrayHelper::getColumn($test_array, 'country');
-		$this->assertThat(
+	$this->assertThat(
-			$result_array,
+		$result_array,
-			$this->equalTo(
+		$this->equalTo(
-				array('United States', 'Germany', 'Canada')
+			array('United States', 'Germany', 'Canada')
-			),
+		),
-			'We did not get the proper column data back'
+		'We did not get the proper column data back'
-		);
+	);
-−
+}
-−
 </source>