Using CDD - Revision history

Aleitner at 12:32, 14 February 2008

2008-02-14T12:32:56Z

← Older revision		Revision as of 12:32, 14 February 2008
Line 70:		Line 70:
	end		end
	</eiffel>		</eiffel>



	= How to restrict test case execution =		= How to restrict test case execution =
Line 77:		Line 75:
	If the ''''Restrict'''' push-button is pressed, only test cases matching the current filter criterion (i.e. test cases that show up in the tree-view) will be executed. You can use this to shorten testing time when working on a particular subset of your program.		If the ''''Restrict'''' push-button is pressed, only test cases matching the current filter criterion (i.e. test cases that show up in the tree-view) will be executed. You can use this to shorten testing time when working on a particular subset of your program.

	= How to run a test case in debug ~~modeest~~ =		= How to run a test case in debug mode =

	To debug a test case, first select it in the test case view and then press the ''Debug selected test routine'' button.		To debug a test case, first select it in the test case view and then press the ''Debug selected test routine'' button.

			= How to delete a test case =

			Test cases or more precisely test routines are regular routines in test classes. In order to delete a test routine simply delete the routine code from the test class. Note that you can easily pick'n'drop the routine into the editor.
			You can also simply pick'n'drop a test routine to the class deletion pebble. Do note however that this always deletes
			the whole class (which may contain other test routines as well).

Aleitner: /* How to add a manual test case */

2008-02-04T22:39:00Z

How to add a manual test case

← Older revision		Revision as of 22:39, 4 February 2008
Line 15:		Line 15:
	= How to add a manual test case =		= How to add a manual test case =

	To add a manual test case simply create a new class whose name contains the word ''''TEST'''', have it inherit from CDD_TEST_CASE and add one or several unit test routines. Make sure that all unit test routines start with ''''test_''''. Here is a simple example test class:		To add a manual test case simply press the ''''Create new manual test case'''' button:

			[[Image:create_test_case.png\|center]]

			Alternatively you can also create a new test case manually. Just create a new class whose name contains the word ''''TEST'''', have it inherit from CDD_TEST_CASE and add one or several unit test routines. Make sure that all unit test routines start with ''''test_''''. Here is a simple example test class:

	<eiffel>		<eiffel>
Line 34:		Line 38:
	</eiffel>		</eiffel>

	After you have added your test class, recompile and your test case should automatially appear in the ''''Testing'''' tool window. ~~A template test case can be created by pressing the ''''Create new manual test case'''' button:~~		After you have added your test class, recompile and your test case should automatially appear in the ''''Testing'''' tool window.

	~~[[Image:create_test_case.png\|center]]~~

	= How to extract a test case =		= How to extract a test case =

Aleitner at 22:36, 4 February 2008

2008-02-04T22:36:47Z

← Older revision		Revision as of 22:36, 4 February 2008
Line 3:		Line 3:
	= Getting Started =		= Getting Started =

	The following will first give a quick overview of the two main features of CDD.		The following will first give a quick overview of the two main features of CDD:

	~~The two main feature of CDD are ''test case exectution'' and ''test case extraction''.~~

	== Test Case Execution ==		== Test Case Execution ==
Line 14:		Line 12:
	CDD observs the developer while running the program under development. Whenever an exception is thrown CDD gets activated automatically and extracts a test cases that is able to reproduce the observed failure. Once a test case is extracted it shows up in the test case view and behaves like an ordinary manually written test cases.		CDD observs the developer while running the program under development. Whenever an exception is thrown CDD gets activated automatically and extracts a test cases that is able to reproduce the observed failure. Once a test case is extracted it shows up in the test case view and behaves like an ordinary manually written test cases.

	~~[[Image:enable_cdd.png\|center]]~~

	The two main features of CDD are test case execution and test case extraction. The first will cause the execution of your test cases after every compilation and the second will extract a new test case after every exception is thrown. By default both features are disabled. Enable both by pressing the two toolbar buttons marked in red below:

	~~[[Image:enable_exec_and_extract.png\|center]]~~

	= How to add a manual test case =		= How to add a manual test case =

Aleitner at 22:35, 4 February 2008

2008-02-04T22:35:18Z

← Older revision		Revision as of 22:35, 4 February 2008
Line 3:		Line 3:
	= Getting Started =		= Getting Started =

	The following will first give a quick overview of the two main features of CDD ~~and then guide you through enabling and using them~~.		The following will first give a quick overview of the two main features of CDD.

	The two main feature of CDD are ''test case exectution'' and ''test case extraction''.		The two main feature of CDD are ''test case exectution'' and ''test case extraction''.

Aleitner: /* How to debug a test case */

2008-01-28T15:42:59Z

How to debug a test case

← Older revision		Revision as of 15:42, 28 January 2008
Line 82:		Line 82:
	If the ''''Restrict'''' push-button is pressed, only test cases matching the current filter criterion (i.e. test cases that show up in the tree-view) will be executed. You can use this to shorten testing time when working on a particular subset of your program.		If the ''''Restrict'''' push-button is pressed, only test cases matching the current filter criterion (i.e. test cases that show up in the tree-view) will be executed. You can use this to shorten testing time when working on a particular subset of your program.

	= How to ~~debug~~ a test case =		= How to run a test case in debug modeest =

	To debug ...		To debug a test case, first select it in the test case view and then press the ''Debug selected test routine'' button.

Aleitner: /* Getting Started */

2008-01-28T15:40:41Z

Getting Started

← Older revision		Revision as of 15:40, 28 January 2008
Line 5:		Line 5:
	The following will first give a quick overview of the two main features of CDD and then guide you through enabling and using them.		The following will first give a quick overview of the two main features of CDD and then guide you through enabling and using them.

	The two main feature of CDD are test case exectution and test case extraction~~. The first brings full IDE support for unit testing as known by the xUnit family tools to EiffelStudio. The second adds a novel feature: new test cases are ''extracted~~'' ~~completely automatically from while the developer programs~~.		The two main feature of CDD are ''test case exectution'' and ''test case extraction''.

			== Test Case Execution ==

	~~CDD~~ adds ~~two new tool windows, named~~ ''''~~Testing~~'''' and ''''~~CDD Output~~'''' ~~to EiffelStuio~~. ~~By default they~~ are ~~not visible~~. ~~Make them visible by going~~ to the ~~menu ''''View -> Tools''''~~ and ~~select ''''Testing'''' and ''''CDD Output'''':~~		This adds full unit testing support to EiffelStudio. It is similar to the xUnit family of testing tools. Each test case that contains the word ''''TEST'''' in its name and inherits from class ''''CDD_TEST_CASE'''' is automatically considered a test class. Test cases are autmatically executed after every compilation. Execution can be restricted, disabled and individual test cases can be started in debug mode.

			== Test Case Extraction ==
			CDD observs the developer while running the program under development. Whenever an exception is thrown CDD gets activated automatically and extracts a test cases that is able to reproduce the observed failure. Once a test case is extracted it shows up in the test case view and behaves like an ordinary manually written test cases.

	[[Image:enable_cdd.png\|center]]		[[Image:enable_cdd.png\|center]]

Aleitner: /* How to restrict test case execution */

2008-01-28T15:35:59Z

How to restrict test case execution

← Older revision		Revision as of 15:35, 28 January 2008
Line 77:		Line 77:

	If the ''''Restrict'''' push-button is pressed, only test cases matching the current filter criterion (i.e. test cases that show up in the tree-view) will be executed. You can use this to shorten testing time when working on a particular subset of your program.		If the ''''Restrict'''' push-button is pressed, only test cases matching the current filter criterion (i.e. test cases that show up in the tree-view) will be executed. You can use this to shorten testing time when working on a particular subset of your program.

			= How to debug a test case =

			To debug ...

Aleitner: /* How to add a manual test case */

2008-01-28T15:35:37Z

How to add a manual test case

← Older revision		Revision as of 15:35, 28 January 2008
Line 37:		Line 37:
	</eiffel>		</eiffel>

	After you have added your test class, recompile and your test case should automatially appear in the ''''Testing'''' tool window. A template test case can created by pressing the ''''Create new manual test case'''' button:		After you have added your test class, recompile and your test case should automatially appear in the ''''Testing'''' tool window. A template test case can be created by pressing the ''''Create new manual test case'''' button:

	[[Image:create_test_case.png\|center]]		[[Image:create_test_case.png\|center]]

Aleitner: /* Getting Started */

2008-01-28T15:34:03Z

Getting Started

← Older revision		Revision as of 15:34, 28 January 2008
Line 2:		Line 2:

	= Getting Started =		= Getting Started =

			The following will first give a quick overview of the two main features of CDD and then guide you through enabling and using them.

			The two main feature of CDD are test case exectution and test case extraction. The first brings full IDE support for unit testing as known by the xUnit family tools to EiffelStudio. The second adds a novel feature: new test cases are ''extracted'' completely automatically from while the developer programs.


	CDD adds two new tool windows, named ''''Testing'''' and ''''CDD Output'''' to EiffelStuio. By default they are not visible. Make them visible by going to the menu ''''View -> Tools'''' and select ''''Testing'''' and ''''CDD Output'''':		CDD adds two new tool windows, named ''''Testing'''' and ''''CDD Output'''' to EiffelStuio. By default they are not visible. Make them visible by going to the menu ''''View -> Tools'''' and select ''''Testing'''' and ''''CDD Output'''':

Aleitner at 15:30, 28 January 2008

2008-01-28T15:30:59Z

← Older revision		Revision as of 15:30, 28 January 2008
Line 7:		Line 7:
	[[Image:enable_cdd.png\|center]]		[[Image:enable_cdd.png\|center]]

	The two main features of CDD are test case execution and test case extraction. The first will cause the execution of your test cases after every compilation and the second will extract a new test case after every exception. By default both features are disabled. Enable both by pressing the two toolbar buttons marked in red below:		The two main features of CDD are test case execution and test case extraction. The first will cause the execution of your test cases after every compilation and the second will extract a new test case after every exception is thrown. By default both features are disabled. Enable both by pressing the two toolbar buttons marked in red below:

	[[Image:enable_exec_and_extract.png\|center]]		[[Image:enable_exec_and_extract.png\|center]]