unit--, a unit test framework for C++

V

VvanN

hi, fellows

I'd like to intruduce a new unit test framework for C++
freely available at:

http://unit--.sourceforge.net/

It does not need bothering test registration, here is an example

// --- begin code ---
#include "unit--.h"

testSuite(MySuite);

testCase(CompareCase, MySuite)
{
int x = 1;
int y = x + 2;
assertTrue(x < y);
}
// --- end code ---

besides, unit-- is implemented entirely in std C++, thus is portable
across different platforms and compilers
 
P

Phlip

VvanN said:
I'd like to intruduce a new unit test framework for C++
freely available at:

http://unit--.sourceforge.net/

It does not need bothering test registration, here is an example

Righteous. CppUnit mires itself in endless test registration issues, instead
of simply using macros to achieve the Test Collector pattern.
// --- begin code ---
#include "unit--.h"

testSuite(MySuite);

testCase(CompareCase, MySuite)
{
int x = 1;
int y = x + 2;
assertTrue(x < y);
}
// --- end code ---

Suppose I had two suites and wanted to run the same case over both suites?

http://c2.com/cgi/wiki?AbstractTest

besides, unit-- is implemented entirely in std C++, thus is portable
across different platforms and compilers

Contrarily, at error time, your editor should present the option to navigate
to a failure, the same as syntax errors.
 
D

Dave Steffen

Phlip said:
Righteous. CppUnit mires itself in endless test registration issues, instead
of simply using macros to achieve the Test Collector pattern.

Those interested in such things might also check out the Boost unit
test framework <http://www.boost.org/libs/test/doc/index.html>; I've
had very good results using it.

----------------------------------------------------------------------
Dave Steffen, Ph.D. Fools ignore complexity.
Software Engineer IV Pragmatists suffer it.
Numerica Corporation Some can avoid it.
ph (970) 419-8343 x27 Geniuses remove it.
fax (970) 223-6797 -- Alan Perlis
dgsteffen at numerica dot us
 
V

VvanN

Phlip said:
Righteous. CppUnit mires itself in endless test registration issues, instead
of simply using macros to achieve the Test Collector pattern.


Suppose I had two suites and wanted to run the same case over both suites?

http://c2.com/cgi/wiki?AbstractTest

Suppose a test case uses std::basic_string<>. How would I run the test case
twice, once with char and again with wchar_t?
we might consider that they are different test cases,
but they have code in common.

"extract method"
(http://www.refactoring.com/catalog/extractMethod.html)
could work for this scenario.
assertTrue() can effect in functions invoked by a testCase

here is an example:

// --- begin code ---
#include <vector>
#include <numeric>
#include <algorithm>
#include "../unit--.h"

testSuite(TemplateSuite)

template <typename T>
void testAlgorithms()
{
using namespace std;
using namespace unit_minus;
vector<T> ve(100, 1);
partial_sum(ve.begin(), ve.end(), ve.begin());

assertTrue(ve.size() > 0);
assertTrue(1 == ve[0]);
for (unsigned i = 1; i < ve.size(); ++i) {
assertTrue(ve[i - 1] + 1 < ve);
}
}

namespace {
testCase(IntCase, TemplateSuite)
{
testAlgorithms<int>();
}

testCase(UnsignedCase, TemplateSuite)
{
testAlgorithms<unsigned>();
}

} // namespace
// --- end code ---
 
P

Phlip

VvanN said:
testSuite(TemplateSuite)

template <typename T>
void testAlgorithms()
{
using namespace std;
using namespace unit_minus;
vector<T> ve(100, 1);
partial_sum(ve.begin(), ve.end(), ve.begin());

assertTrue(ve.size() > 0);
assertTrue(1 == ve[0]);
for (unsigned i = 1; i < ve.size(); ++i) {
assertTrue(ve[i - 1] + 1 < ve);
}
}

namespace {
testCase(IntCase, TemplateSuite)
{
testAlgorithms<int>();
}

testCase(UnsignedCase, TemplateSuite)
{
testAlgorithms<unsigned>();
}

} // namespace
// --- end code ---


Thanks!

One use of AbstractTest is to turn a cases' setUp() and tearDown() into an
abstract factory. setUp() will create a different type, so a common case
body can work across a range of types. Your code doesn't need this effect
because your assertions are not members of the basic TestCase class.

(Assertions are typically macros, so I mean macros are members when they use
member variables inside them.)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,734
Messages
2,569,441
Members
44,832
Latest member
GlennSmall

Latest Threads

Top