WinUnit

New Comment on "Create your first test project"

rdawson999 — Fri, 16 Nov 2012 16:41:56 GMT

Try using the x86 Winunit.exe instead of the 64 bit version.

Commented Issue: Feature Request: Create a Visual Studio Add-in [9733]

icnocop — Thu, 11 Oct 2012 01:04:49 GMT

I'd like to request that a WinUnit Visual Studio Add-in be created so that unit testing can be integrated with the IDE similar to mstest unit test integration.
 
For example, here is an add-in for google's test framework: http://googletestaddin.codeplex.com.
 
It adds three buttons and three items to the code context menu:
"Execute all test"
"Execute the selected test"
"Debug the selected test"

Comments: ** Comment from web user: icnocop **

@smibe, Thank you very much for the link! :D

Commented Issue: Feature Request: Create a Visual Studio Add-in [9733]

smibe — Wed, 10 Oct 2012 14:32:40 GMT

There is VisualAssert (http://www.visualassert.com/unit-testing-framework/) which can be used to run tests.

Source code checked in, #80132

Project Collection Service Accounts — Mon, 01 Oct 2012 21:49:39 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #80131

Project Collection Service Accounts — Mon, 01 Oct 2012 21:43:10 GMT

Checked in by server upgrade

Reviewed: WinUnit 1.2.0909.1 (Sep 24, 2012)

hansrwindhoff — Mon, 24 Sep 2012 16:04:54 GMT

Rated 5 Stars (out of 5) - Very nice, light weight and power full. Easy to use.

New Comment on "Create your first test project"

Macpeters — Thu, 20 Sep 2012 00:05:33 GMT

I am getting LoadLibraryW failed - no tests were run. Has anyone else gotten this?

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

Created Issue: Feature Request: automatically display the datetime started and duration of unit tests [9790]

icnocop — Sat, 07 Jan 2012 19:44:16 GMT

I'd like to request that WinUnit automatically display the datetime each unit test was started and its duration. Also, the combined timespan for the duration of all the tests would also be nice.

Thank you.

Created Issue: Feature Request: Create a Visual Studio Add-in [9733]

icnocop — Tue, 20 Dec 2011 01:42:53 GMT

I'd like to request that a WinUnit Visual Studio Add-in be created so that unit testing can be integrated with the IDE similar to mstest unit test integration.

For example, Here is an add-in for google's test framework: http://googletestaddin.codeplex.com.

It adds three buttons and three items to the code context menu:
"Execute all test"
"Execute the selected test"
"Debug the selected test"

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?

Created Issue: Feature Request: return a non-zero exit code if LoadLibraryW fails and\or if no tests were run [8805]

icnocop — Fri, 17 Jun 2011 02:07:33 GMT

Hi.

Thank you for WinUnit 1.2.0909.1.

I would like to request that WinUnit.exe return a non-zero exit code if LoadLibraryW fails andor\ no tests were run to indicate an error\failure.

For example, if I create a dll with an invalid manifest file and pass it to WinUnit.exe, i get the following output:

WinUnit.exe -n MyCppTests.dll
Processing [MyCppTests.dll]...
[WinUnit] WinUnitLib::TestModule::GetModule: LoadLibraryW failed on C:\MyCppTests\MyCppTests.dll.
[MyCppTests.dll] No tests were run.

No tests were found.

However, WinUnit.exe exits with a 0 return code, which is not expected. I expected it to be non-zero to indicate an error\failure.

Thank you.

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

Commented Feature: Provide a project template to support CRT debugging features [4220]

icnocop — Thu, 31 Mar 2011 03:08:57 GMT

There have been suggested to support the Debug CRT for detecting memory leaks. Basically it requires two modifications the the test dll project.

First, add the following lines to the test dll's stdafx.h file:
#define _CRTDBG_MAP_ALLOC
#include <crtdbg.h>

And second, insert the following as the first line in the test dll's main .cpp dll file:
_CrtSetDbgFlag( _CRTDBG_ALLOC_MEM_DF | _CRTDBG_LEAK_CHECK_DF);

e.g.,

int _tmain(int argc, TCHAR* argv[], TCHAR* envp[])
{
_CrtSetDbgFlag( _CRTDBG_ALLOC_MEM_DF | _CRTDBG_LEAK_CHECK_DF);
int nRetCode = 0;

.
Comments: ** Comment from web user: icnocop **

_tmain is an entry point for an application, not a dll.

I followed the steps here:
Finding Memory Leaks Using the CRT Library
http://msdn.microsoft.com/en-us/library/x98tx3cf.aspx

I called "_CrtSetDbgFlag ( _CRTDBG_ALLOC_MEM_DF | _CRTDBG_LEAK_CHECK_DF );" within BEGIN_TEST(){ ... }END_TEST but could not get the file and the line number where the leaked memory is first allocated.

Any ideas?

Thank you.