winunit Issue Tracker Rss Feed

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.

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"

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.

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.

Created Issue: WIN_ASSERT_NOT_THROWS macro [6615]

magnetall — Mon, 28 Jun 2010 08:10:27 GMT

Is it possible add WIN_ASSERT_NOT_THROWS macro?
Some times it is usefull

Created Issue: Error loading a custom logger with absolute path [5711]

JohannesU — Thu, 08 Apr 2010 08:41:35 GMT

It is not possible to load a custom logger with an external path for example:

WinUint.exe -l c:\customlogger.dll:out.txt sometest.dll

The problem is the handling of the ':' in the path in ExternalLogger.cpp line 62:

const wchar_t* delimiterPosition = wcschr(reference, L':');

This line splits of only 'c' but not the whole path.

Closed Issue: WinUnit.chm empty in WinUnit-1.2.0909.1 [5318]

mkblees — Fri, 05 Feb 2010 00:42:53 GMT

The unzipped archive contains Documentation\WinUnit.chm. All pages show error message

"Navigation to the webpage was canceled

What you can try:
Retype the address. "
Comments:

I believe this is issue can be resolved by unblocking the CHM.

Commented Issue: WinUnit.chm empty in WinUnit-1.2.0909.1 [5318]

mkblees — Fri, 05 Feb 2010 00:41:59 GMT

The unzipped archive contains Documentation\WinUnit.chm. All pages show error message

"Navigation to the webpage was canceled

What you can try:
Retype the address. "
Comments: ** Comment from web user: mkblees **

Hi Paul,
Try right-clicking on the CHM file in Windows Explorer and select Properties. You should see a button that says "Unblock". If you click that you should be able to see the content. Let us know if you have further problems.
Maria

Created Issue: WinUnit.chm empty in WinUnit-1.2.0909.1 [5318]

PaulS609 — Tue, 02 Feb 2010 08:24:20 GMT

The unzipped archive contains Documentation\WinUnit.chm. All pages show error message

"Navigation to the webpage was canceled

What you can try:
Retype the address. "

Closed Issue: Problem when using MFC objects within the Test DLL project [4221]

Jhualpa — Mon, 19 Oct 2009 04:31:11 GMT

It seems to be an #include hell order, which does not allow to compile a test project that consumes MFC classes from another project, whether it is linked to MFC dynamically or statically. There is a problem with #include <windows.h>, it needs further research.
Comments:

This issue rises if you create your WinUnit project using an MFC empty DLL with precompiled headers. If WinUnit projects follow the project template described on the homepage the include hell problem goes away. So always create WinUnit projects starting from a C++ empty project.

Commented Issue: Problem when using MFC objects within the Test DLL project [4221]

Jhualpa — Mon, 19 Oct 2009 04:30:25 GMT

Commented Issue: WIN_ASSERT_TRUE only expects strings [4432]

Jhualpa — Mon, 19 Oct 2009 04:24:53 GMT

This macro only expects strings. However other unit testing frameworks have this macro for numeric values. Currently if I pass in numeric values to this I get build errors. I want to compile at warning level 4, and this macro is getting in the way of that.

So for instance, I want to be able to do this:

WIN_ASSERT_EQUAL( 1, foo->GetNum() );
Comments: ** Comment from web user: Jhualpa **

Chis, your issue seems confusing. WIN_ASSERT_TRUE only expects a condition that evaluates to true or false, and WIN_ASSERT_EQUAL accepts both numeric values and strings as well. Try this sample tests I have developed, I did compiled them with warning level 4 and no issues.

#include "WinUnit.h"
#include "string.h"

BEGIN_TEST(WIN_ASSERT_TRUE_With_Numbers)
{
WIN_ASSERT_TRUE(4 == 4);
}
END_TEST

BEGIN_TEST(WIN_ASSERT_TRUE_With_Strings)
{
WIN_ASSERT_TRUE(strcmp("4","4")==0);
}
END_TEST

BEGIN_TEST(WIN_ASSERT_EQUAL_With_Numbers)
{
WIN_ASSERT_EQUAL(4, 4);
}
END_TEST

BEGIN_TEST(WIN_ASSERT_EQUAL_With_Strings)
{
WIN_ASSERT_EQUAL("4","4");
}
END_TEST

Created Issue: WIN_ASSERT_TRUE only expects strings [4432]

chrisJohnson — Sat, 10 Oct 2009 07:04:37 GMT

Closed Issue: Missing .SLN file on the \Release\Examples Directory [4219]

mkblees — Thu, 10 Sep 2009 07:59:46 GMT

There is not .sln file that links the samples published on the \Release\Examples directory. Besides WinUnit does not get executed on the TestSampleLib project.
Comments:

Rearranged directories, adding a new VS2008 directory under Release. Included a copy of this file (branched from Development\Current).

Commented Issue: Missing .SLN file on the \Release\Examples Directory [4219]

mkblees — Thu, 10 Sep 2009 05:57:45 GMT

There is not .sln file that links the samples published on the \Release\Examples directory. Besides WinUnit does not get executed on the TestSampleLib project.
Comments: Associated with changeset 29390.

Reopened Issue: Missing .SLN file on the \Release\Examples Directory [4219]

mkblees — Thu, 10 Sep 2009 05:55:55 GMT

There is not .sln file that links the samples published on the \Release\Examples directory. Besides WinUnit does not get executed on the TestSampleLib project.
Comments: ** Comment from web user: mkblees **

Reopening so I can associate some checkins with it (recreating Examples.sln in Development directory and entire Release branch).

Closed Issue: Issue in macros if a string contains "%" [4210]

mkblees — Thu, 10 Sep 2009 05:32:41 GMT

From Konstantin Izmailov, Feb. 14, 2008:

"
I’m using WinUnit and found a bug. Here is part of my test code:
WIN_ASSERT_TRUE(0 == wcscmp(pwszExpectedResult, pwszActualResult), _T("Actual result is differenet from expected\n\tsource: %s\n\tactual: %s\n\texpected: %s"), pwszSrcText, pwszActualResult, pwszExpectedResult);

Problem occurs when any of the test string are having ‘%’ sign, for example,
pwszSrcText = L"select * from accountid id, account a from account where accountid='DEMO00000001' or account like 'Ab%'"

Underlying _snwprintf_s routine throws assertion: “Incorrect format specifier”.

Fix can be made in WinUnit.h at Line 115 as shown below:
EMIT_ERROR(_T("%s"), e.Message()); \
"
Comments: Resolved with changeset 29388.

Closed Issue: Some ASSERT macros use const T where they should use const T& [4205]

mkblees — Thu, 10 Sep 2009 05:03:52 GMT

From David Connet, Jan. 14, 2008:

"
I just ran into some issues using WIN_ASSERT_EQUAL - since the template
is defined as 'const T ...', this actually causes a copy constructor to
be invoked. I discovered this when using it to compare some boost smart
points on classes where all the ctors are protected. I can work around
it be doing "WIN_ASSERT_TRUE(*obj1 == *obj2);"
"
Comments: Resolved with changeset 29387.