Unit Test Tutorial 1 - Revision history

Cmb: Several markup changes. URL corrections.

2022-12-02T23:15:39Z

Several markup changes. URL corrections.

2010-05-25T06:04:40Z

Link to Tutorial Part 2

← Older revision		Revision as of 06:04, 25 May 2010
Line 216:		Line 216:
	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].

			= Unit Test Tutorial 2 =
			This article is continued here: [[Unit Test Tutorial 2]]. This includes looking into the derived 'PHPUnit_Framework_TestCase' testclass and the minimum requirements for a standalone testclass.


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

2010-05-24T14:36:33Z

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

2010-05-24T14:35:14Z

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

2010-05-24T02:53:52Z

Add to category 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]]

2010-05-24T02:49:11Z

How a Unit Test should NOT be written

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

2010-05-24T02:40:35Z

Add new Chapter

← Older revision		Revision as of 02:40, 24 May 2010
Line 212:		Line 212:
	}		}
	</source>		</source>

			== How a Unit Test should NOT be written ==

2010-04-19T02:44:24Z

Running Tests

← Older revision		Revision as of 02:44, 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.		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 ==

2010-04-19T02:43:44Z

Running Tests

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

2010-04-19T02:40:15Z

3. Tests assertions about the results (outputs)

← Older revision		Revision as of 02:40, 19 April 2010
Line 199:		Line 199:
	)		)
	);		);

	$result_array = JArrayHelper::getColumn($test_array, 'country');		$result_array = JArrayHelper::getColumn($test_array, 'country');

	$this->assertThat(		$this->assertThat(
	$result_array,		$result_array,