Writing Tests ^

1 include ASSERT-macros: ^

 #include "cute.h"

2 code your test functions or functors ^

see CuTe for details

3 collect your tests in a cute::test_suite ^

    cute::test_suite s;

• suites are vectors of tests, so just append the tests
• wrap test functions using the macro CUTE()

      s.push_back(CUTE(mytestfunction));
  

• test functors can be added without "cuteifying". Note you need to instantiate a functor object.

      s.push_back(mytestfunctor());
  

• you might consider collecting your suite's in a make_suite function or method.

Running Tests ^

You need to provide a main()-function for running your tests.

0 include the necessary infrastructure ^

#include "cute_runner.h"
#include "cute_counting_listener.h"
#include "vstudio_listener.h"

• N.B.: vstudio_listener.h also works with a gnu environment. it then just uses stdout/stderr for reporting.

1 instantiate a Runner with an appropriate Listener ^

    runner<counting_listener<vstudio_listener> > run;

2 pass your test_suite to the runner for running them ^

    run(s);

observe the outcome...

Extending CuTe ^

• ideas are: other customized listeners for timing tests, generating other output formats,

Todos for CuTe ^

• test on other platforms (linux, macosx, ...) DONE
• automake (?) for tests of cute.
• more elaborate treatment of floating point numbers. May steal ideas from boost's unit testing framework. DONE through using traits and template meta programming, automatic selection of a delta, if comparing floating point numbers without specifying one.
• better integration with IDE's DONE see http://cute-test.com
  • visual studio "integration" if run in debug mode (F5) - click on error message to navigate to a failing test