Re: Unit Testing in C++

From:

James Kanze <james.kanze@gmail.com>

Newsgroups:

comp.lang.c++

Date:

Tue, 24 Jun 2008 14:31:09 -0700 (PDT)

Message-ID:

<5d03e9d5-1c2f-4a04-81e7-28ae9dc663eb@x35g2000hsb.googlegroups.com>

On Jun 24, 5:53 pm, Noah Roberts <u...@example.net> wrote:

earthwormgaz wrote:

James Kanze wrote:

It's not too clear to me what your deliverables are, but
generally, you should organize your directory structure so that
everything in a given directory can be tested together. If you
need a mock something, then that something should normally be
from a different directory, and not part of the code being
developed in the same directory.

Hmm, I'd come to think that I wanted to mock everything around the
class under test. You seem to be saying mock around the system that
includes the class under test, unless you have to do otherwise.

I don't think the person you are replying to fully understands the
purpose of unit tests.

That from you?

You definitely do want to test each unit individually; there
should be a test for each public class at the least.

Hmmm, the name is "unit test", not class test. You want to test
each unit more or less individually. On the other hand, you can
generally consider lower level stuff as "part of the system".
(I never try to mock std::vector, for example. I just suppose
that it works.)

This often involves mock objects.

Not if your code is well designed and well engineered. It
sometimes involves mock objects, but I find that with good
design, it this isn't the case that frequently.

--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34