1 Although Catch allows you to group tests together as sections within a test case, it can still be convenient, sometimes, to group them using a more traditional test fixture. Catch fully supports this too. You define the test fixture as a simple structure:
4 class UniqueTestsFixture {
10 UniqueTestsFixture() : conn(DBConnection::createConnection("myDB")) {
18 int UniqueTestsFixture::uniqueID = 0;
20 TEST_CASE_METHOD(UniqueTestsFixture, "Create Employee/No Name", "[create]") {
21 REQUIRE_THROWS(conn.executeSQL("INSERT INTO employee (id, name) VALUES (?, ?)", getID(), ""));
23 TEST_CASE_METHOD(UniqueTestsFixture, "Create Employee/Normal", "[create]") {
24 REQUIRE(conn.executeSQL("INSERT INTO employee (id, name) VALUES (?, ?)", getID(), "Joe Bloggs"));
28 The two test cases here will create uniquely-named derived classes of UniqueTestsFixture and thus can access the `getID()` protected method and `conn` member variables. This ensures that both the test cases are able to create a DBConnection using the same method (DRY principle) and that any ID's created are unique such that the order that tests are executed does not matter.