Debugging Unit Tests - Revision history

MakoBot: Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name

2012-03-04T06:20:15Z

Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name

2012-03-04T02:56:49Z

Robot: Cosmetic changes

2011-06-10T14:20:44Z

Removed 'Template:' prefix from template includings and/or changed external-link into internal-link

2009-06-24T08:47:03Z

2009-05-21T14:10:51Z

2009-01-05T18:44:42Z

‎Debugging Unit Tests with Visual Studio Express 2008

2009-01-05T18:37:45Z

‎Debugging Unit Tests with Visual Studio

2009-01-04T10:36:25Z

‎Debugging Unit Tests with Visual Studio

2009-01-03T17:04:14Z

‎Debugging Unit Tests with Vistual Studio

2009-01-03T17:02:45Z

@@ Line 32: / Line 32: @@
 ) Open project and choose the test dll you want from OpenSim/bin directory (for example OpenSim.Data.MySQL.Tests.dll)
-) Open your OpenSim solution to Visual Studio.
+) Open your OpenSimulator solution to Visual Studio.
 ) Attach NUnit GUI process to Visual Studio by choosing Debug -> Attach to Process.
@@ Line 76: / Line 76: @@
 == Debugging using TestDriven.net ==
-OpenSim comes with a "testing" file that mentions a tool name "TestDriven.net". It looks good when you visit the page (http://www.testdriven.net) and there is a lot of positive feedback about it.
+OpenSimulator comes with a "testing" file that mentions a tool name "TestDriven.net". It looks good when you visit the page (http://www.testdriven.net) and there is a lot of positive feedback about it.
 Anybody who has experience with it: please write a bit about it here.
 Unfortunately it is a plugin and it seems that Microsoft removed support for plugins from Visual Studio 2008 Express (the free edition). So if you are working with this (like I) TestDriven.net unfortunately isn't an option.

@@ Line 55: / Line 55: @@
 . Find the file XXX.csproj.user where XXX is the DLL that holds your unit tests.
-. Open it with an editor and find the   "<PropertyGroup>" tag.
+. Open it with an editor and find the "<PropertyGroup>" tag.
 . Add the following lines beyond the <PropertyGroup> tag:

@@ Line 1: / Line 1: @@
 __NOTOC__
-{{Template:Quicklinks}}
+{{Quicklinks}}
 <br />
 Debugging unit tests is useful for both test driven development and resolving build failures.

← Older revision		Revision as of 08:47, 24 June 2009
Line 5:		Line 5:

	== Debugging Unit Tests with Visual Studio ==		== Debugging Unit Tests with Visual Studio ==
		+
		+	=== Visual Nunit Addin (Open Source) ===
		+
		+	1) Download and install Visual Nunit: http://www.bubblecloud.org/visualnunit
		+
		+	2) Open Solution in Visual Studio.
		+
		+	3) Ensure that your projects have copy local enabled on all dependencies which are not in GAC. (Tests are executed in project bin/Debug folder)
		+
		+	4) Open NUnit View from menu: View -> Other Windows -> NUnit View
		+
		+	If no tests are visible then projects do not contain NUnit tests or dependencies are not available in project/bin/Debug folder.
		+
		+	6) Start debugging by clicking the red arrow in the beginning of the test row.
		+
		+	7) Debug as you would debug any executable on Visual Studio.
		+
		+	=== NUnit GUI ===

	1) Download and install NUnit which includes NUnit GUI.		1) Download and install NUnit which includes NUnit GUI.

← Older revision		Revision as of 14:10, 21 May 2009
Line 1:		Line 1:
		+	__NOTOC__
		+	{{Template:Quicklinks}}
		+	<br />
	Debugging unit tests is useful for both test driven development and resolving build failures.		Debugging unit tests is useful for both test driven development and resolving build failures.

@@ Line 30: / Line 30: @@
 "Obviously" as there is no way to activate this feature from the GUI. But the underlying engines still have all features included that you need. And there is a way to make the necessary settings. The following steps will help you to achieve your goal:
-# Close your solution first, in case you have it open
+. Close your solution first, in case you have it open
-# Find the file XXX.csproj.user where XXX is the DLL that holds your unit tests.
-# Open it with an editor and find the   "<PropertyGroup>" tag.
+. Find the file XXX.csproj.user where XXX is the DLL that holds your unit tests.
-# Add the following lines beyond the <PropertyGroup> tag:
    <PropertyGroup>
      ...
@@ Line 40: / Line 43: @@
      ...
    </PropertyGroup>
 Of course you must put the right path to ''your'' nunit.exe into it.
-# Open the solution again
+. Open the solution again
-# Now set the Test DLL you just modified as "startup project" and press F5. You will get a NUnit GUI running under the debugger. Put breakpoints to your code and debug as you like, let your code run as often as you want .....
 Happy Debugging :-)
 == Debugging using TestDriven.net ==

@@ Line 23: / Line 23: @@
 Note: This seems to be an option for the Professional Editions of Visual Studio. The Express Edition (the free one) seems to have no Debug->Attach to Process option.
 * You might be able to work around this by downloading nunit gui sources and building and running it from the the express edition. You need to have the nunit gui project added to the solution you want to debug.
 == Debugging using TestDriven.net ==

@@ Line 1: / Line 1: @@
 Debugging unit tests is useful for both test driven development and resolving build failures.
-== Debugging Unit Tests with Vistual Studio ==
+== Debugging Unit Tests with Visual Studio ==
 ) Download and install NUnit which includes NUnit GUI.

← Older revision		Revision as of 17:02, 3 January 2009
Line 21:		Line 21:

	Note: This seems to be an option for the Professional Editions of Visual Studio. The Express Edition (the free one) seems to have no Debug->Attach to Process option.		Note: This seems to be an option for the Professional Editions of Visual Studio. The Express Edition (the free one) seems to have no Debug->Attach to Process option.
		+
		+	== Debugging using TestDriven.net ==
		+	OpenSim comes with a "testing" file that mentions a tool name "TestDriven.net". It looks good when you visit the page (http://www.testdriven.net) and there is a lot of positive feedback about it.
		+
		+	Anybody who has experience with it: please write a bit about it here.
		+
		+	Unfortunately it is a plugin and it seems that Microsoft removed support for plugins from Visual Studio 2008 Express (the free edition). So if you are working with this (like I) TestDriven.net unfortunately isn't an option.