I’ve been using Boost.Test until I find/create a true BDD solution.

e.g.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
//Specification source file
...
class steps {
public:
// Givens
void GivenIHaveNotCollectedAnyMoney() {}

void GivenThereIsOneMemberInTheSystem(const std::string& member_name) {
member_repository_.removeAllMembers();
member_repository_.addMember(member_name);
}

//Whens
void WhenIStartTheApplication() {
CoffeeFundCGIApp app(member_repository_, output_stream_);
}

//Thens
void ThenIShouldSeeAMenuWithMember(const std::string& member_name) {
verifyHeader();
HTMLExpert daveRagett(outputAsString().substr(25));
BOOST_CHECK(daveRagett.doesOutputContainAMenuWithChoices(member_name));
}
...
};

...

BOOST_FIXTURE_TEST_CASE( scenarioStartCollectingWithOneMember, steps )
{
GivenThereIsOneMemberInTheSystem(“DeNigris”);
WhenIStartTheApplication();
ThenIShouldSeeAMenuWithMember(“DeNigris”);
}

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
//CoffeeFundCGIApp specification file
...
BOOST_AUTO_TEST_CASE( shouldOutputMenuWithOneMember )
{
MemberRepositoryForTesting member_repository;
std::ostringstream output;
CoffeeFundCGIApp app(member_repository, output);
HTMLExpert daveRagett(output.str().substr(25));
BOOST_CHECK(daveRagett.doesOutputContainAMenuWithChoices(member_repository.member_name));
}

As you can see, I’ve noticed when implementing BDD, often my app controller tests and high-level features are almost duplicates of each other. What is the point of having both, if any, unless you’re mocking classes out? Which I’m not doing because the ostringstream is easier to use than to mock.

Thanks for your kind words. I took a look at your blog and I’m really pleased you are looking at domain-driven design – it was a real awakening for me. The combination of a strong domain model and a focus on delivering value to stakeholders is unbeatable.

Let me know how you get on with this stuff in C++. I know the tool support isn’t as strong for much of the process automation, although having said that, make(1) has been around for about 25 years!

Thanks for the awesome work on BDD. It really maximizes the benefits of TDD.

With the ever-shortening software release cycles, assuring the quality of codes, while managing the cost and risks involved, is a major challenge faced by a majority of software development enterprises nowadays. With project life cycles decreasing even…