winunit Discussions Rss Feed

New Post: The new "Native Unit Test Project" in Visual Studio 11

icnocop — Sat, 10 Mar 2012 05:42:29 GMT

I noticed there is a new “Native Unit Test Project” in Visual Studio 11 Developer Preview\Beta

Here is some preliminary documentation on msdn:

Unit testing native code with Unit Test Explorer

http://msdn.microsoft.com/en-us/library/hh270864%28v=vs.110%29.aspx

New Post: using WinUnit and registration free COM activation

icnocop — Fri, 01 Jul 2011 19:53:35 GMT

I asked the question on StackOverflow here:

http://stackoverflow.com/questions/6393865/registration-free-com-without-copying-the-dll-to-the-same-directory-as-the-execut

New Post: using WinUnit and registration free COM activation

icnocop — Fri, 17 Jun 2011 03:46:18 GMT

I got this to work by following the guide here:

http://www.mazecomputer.com/sxs/help/sxsapi3.htm

And also example code from vvvsample here:

http://msf.codeplex.com/

There is only one caveat: I have to copy the COM dll to the same directory as WinUnit.exe.

I am currently passing the full path of the external manifest and the full path of the test directory to CActCtxHandle.Create() (ex. "C:\MyCppTests\Release\MyCppTests.dll.manifest" and "C:\MyCppTests\Release" respectively).

The COM dll also resides in "C:\MyCppTests\Release" but WinUnit.exe resides in a different directory (ex. "C:\WinUnit").

Any ideas?

New Post: using WinUnit and registration free COM activation

icnocop — Thu, 16 Jun 2011 22:58:38 GMT

I found another answer that indicates it is possible in one of two ways:

http://stackoverflow.com/questions/1770463/how-to-do-registration-free-com-in-a-plug-in-architecture

New Post: using WinUnit and registration free COM activation

icnocop — Thu, 16 Jun 2011 22:52:44 GMT

I found an answer that indicates this is not possible:

http://stackoverflow.com/questions/4935536/nunit-test-with-fortran-dll

New Post: using WinUnit and registration free COM activation

icnocop — Thu, 16 Jun 2011 21:10:07 GMT

Hi.

I am trying to create a unit test that instantiates a COM object using registration free (reg-free) activation.

Is this possible without modifying WinUnit.exe or creating WinUnit.exe.manifest for example?

WinUnit 1.2.0909.1

Thank you.

New Post: Using winUnit for .c files

kriscsc09 — Wed, 01 Jun 2011 02:54:31 GMT

Hello!

I have been searching on how to use WinUnit for .c files.

But, all the documentations that I came across were C++ files.

Are there any documentations on how to use WinUnit for .c files?

Are there specific Macros used for .c files?

Thank you.

New Post: testing a MFC-Dll with com and serialisation

icnocop — Thu, 31 Mar 2011 19:39:59 GMT

Calling CoInitialize and AFX_MANAGE_STATE(AfxGetStaticModuleState()); is application specific.

You can always create your own methods\macros that wrap around the winunit macros so that they call your application specific functions.

New Post: step by step

icnocop — Thu, 31 Mar 2011 19:37:50 GMT

There is a link on the home page.

Getting Started > "Create your first test project"

http://winunit.codeplex.com/wikipage?title=Create%20your%20first%20test%20project&referringTitle=Home

New Post: testing a MFC-Dll with com and serialisation

suriel666 — Thu, 17 Mar 2011 12:42:11 GMT

I'm testing winUnit since a couple of days and encountered the following "issue" which may be interesting to others as well:

i want to test classes and methods from another dll. to do this i link the .lib into my winunit-testdll and include the needed header.

well... things work until

- the tested dll uses com-components. this fails until i add somewhere "::CoInitialize(0) ;" pretty early in my test-dll (of yourse no winunit-issue but still important to know)

- the tested dll also uses the mfc-serialisation meachanism. i wanted to test that and serialized an object from within the test-dll. every call to deserialisazion failed with an exception. my class could not get created dynamically. well, after some hacking, testing and googleing i found out that you have to:

1. call "InitDllToTest" very early in the testing-dll. this is a call to some function in the tested dll which calls "new CDynLinkLibrary()".

2. call "AFX_MANAGE_STATE(AfxGetStaticModuleState());" in every testfunction as 1st statement bevor you do anything woth MFC-classes. after that (de-)serialisation works for me.

please refer to http://support.microsoft.com/kb/154126

so maybe it would be a good idea to add "AFX_MANAGE_STATE(AfxGetStaticModuleState());"-calls to the winunit-macros so it gets called automatically at every test?

greetings

New Post: step by step

billy17 — Tue, 30 Nov 2010 07:31:02 GMT

can somebody explain the step by step for using the winunit. i have not done unit testing before.

New Post: How do I use the VS macros that come with WinUnit?

diskrete — Sun, 12 Sep 2010 14:58:54 GMT

I’ve created a modified version of the RunningTests macros that fixes the problem. It’s fairly crude as I’m no VS Macro expert, but if anyone else would like to try it, here it is:

http://gist.github.com/576164

New Post: How do I use the VS macros that come with WinUnit?

diskrete — Sat, 11 Sep 2010 23:01:58 GMT

I am trying to use the Visual Studio macros that come with WinUnit.

But when I run (for example) RunTestAtCursor it tells me:

Current function is not a WinUnit test (BEGIN_TEST).

Digging into the macros, I found that it checks whether the function name begins with TEST_.

Unfortunately, the GetCurrentFunctionName function in the VS macro always returns BEGIN_TEST and never the real function name (which will be something like TEST_MyFirstTest). So it won’t run any of my tests. :-(

I am using Visual Studio 2010.

New Post: Test order

magnetall — Mon, 28 Jun 2010 07:49:39 GMT

How to define test run order ?

Thanks

Alex

New Post: Test for classes in an .exe

jhualpa — Wed, 20 Jan 2010 14:40:10 GMT

NielsC,

I want to make sure that I understand your issue. Suppose that you name only the path, how would you expect that the compiler and WinUnit know to which object file to link to ?

By explicity telling the object file to link to, you are adding a reference to that object file into your WinUnit DLL, so it is needed in order to determine the dependencies. But if you have 5 executables why do you explicity link to their classess instead of linking to the .lib that each .exe generates. In that way you will have to name as much as 5 .lib names.

Does this make sense ?

New Post: WinUnit and VS2005

Likurg — Mon, 18 Jan 2010 19:56:23 GMT

Hi again! Tnx for your quick reply.

I tried one more time from the beginning and now it works correctly.

Really, weird thing happened before.

Anyway, thank you for your help.

New Post: WinUnit and VS2005

mkblees — Mon, 18 Jan 2010 15:09:31 GMT

Hi!

I know it definitely works in VS 2005; I think the warning added to winunit.h may have been overly conservative (it was added since some of the features don't compile in older versions). Look in winunit.h and find the error message you saw and try removing that part and see if it works; if so, we should change the error condition.

(BTW your English is great. :))

Maria

New Post: WinUnit and VS2005

Likurg — Mon, 18 Jan 2010 15:02:14 GMT

Hello.

I'd like to use WinUnit with Visual Studio 2005, but, unfortunately,

WinUnit complains, that Compiler Version must be at least 9!

Is it possible to use WinUnit with version 8??

Any help would be highly appreciated.

P.S sorry for my english.

New Post: Timeout

memphix — Mon, 04 Jan 2010 09:54:01 GMT

Hello,

I'm wondering if it's possible to set timout for tests.

If it isn't possible do you have any solution how to end a test when it is still wroking and how to send a message of failed test.

Regards

Dariusz Opitek

New Post: Test for classes in an .exe

NielsC — Sun, 06 Dec 2009 19:35:41 GMT

Hi all,

i have been trying to use WinUnit on classes used in a project released as a number of exe-files.

In "Visual Studio->ProjectProperties->Linker->Addidtional Dependencies" i added the full paths to the ClassName.obj - files (which works), but i would prefer to name only the path and not every single class.

How to?

Our App is split up in a number >10 common libraries (no problem testing these) an five executables.

Can anyone give me a hint how to move on from here?

Regards

Niels Cederstrøm, Kiel, Germany