TheSwamp

Code Red => .NET => Topic started by: Andrey Bushman on August 03, 2010, 06:23:48 AM

Title: Writing tests for .Net AutoCAD plagins via Visual Studio 2010 Test menu tools
Post by: Andrey Bushman on August 03, 2010, 06:23:48 AM

Somebody has experience of writing tests for .Net AutoCAD plagins via Visual Studio 2010 Test menu tools?

If "yes" - then I will be very grateful for samples of it code.

Title: Re: Writing tests for .Net AutoCAD plagins via Visual Studio 2010 Test menu tools
Post by: David Hall on August 03, 2010, 09:14:00 AM

Andrey, I sent you a PM

Title: Re: Writing tests for .Net AutoCAD plagins via Visual Studio 2010 Test menu tools
Post by: Andrey Bushman on August 03, 2010, 09:21:35 AM

Quote from: CmdrDuh on August 03, 2010, 09:14:00 AM

Andrey, I sent you a PM

Yes, I got it, thank's.

Title: Re: Writing tests for .Net AutoCAD plagins via Visual Studio 2010 Test menu tools
Post by: It's Alive! on August 03, 2010, 09:25:17 AM

thanks for sharing  :|

Title: Re: Writing tests for .Net AutoCAD plagins via Visual Studio 2010 Test menu tools
Post by: Andrey Bushman on August 03, 2010, 09:29:12 AM

Quote from: __declspec on August 03, 2010, 09:25:17 AM

thanks for sharing  :|

but... what about it topic? :-)

Title: Re: Writing tests for .Net AutoCAD plagins via Visual Studio 2010 Test menu tools
Post by: David Hall on August 03, 2010, 06:06:51 PM

Quote from: __declspec on August 03, 2010, 09:25:17 AM

thanks for sharing  :|

The PM had nothing to do with the solution.

Title: Re: Writing tests for .Net AutoCAD plagins via Visual Studio 2010 Test menu tools
Post by: It's Alive! on August 03, 2010, 08:13:26 PM

Ah, and here I thought you guys were talking about top secret unit testing techniques via PM  :laugh:

Title: Re: Writing tests for .Net AutoCAD plagins via Visual Studio 2010 Test menu tools
Post by: Andrey Bushman on August 04, 2010, 12:33:30 AM

Somebody use it, or for AutoCAD it's impossible?

Title: Re: Writing tests for .Net AutoCAD plagins via Visual Studio 2010 Test menu tools
Post by: It's Alive! on August 04, 2010, 01:29:31 AM

I have not used it, from what I understand, it's for doing unit testing. You can use it to instantiate classes, run tests then tear down. I would assume its for larger projects and is probably not applicable for plug-ins that only contain a few command methods returning void. For the itty-bitty apps you can use the tools  found in System.Diagnostics; I.e. [Conditional("DEBUG")],  Debug and Trace