From fe963ebcd6473bc67637c1cf974803c30dda9bc5 Mon Sep 17 00:00:00 2001 From: Trevor Hickey Date: Fri, 29 May 2015 13:05:02 -0400 Subject: [PATCH] fixes spacing tutorial.md --- docs/tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorial.md b/docs/tutorial.md index 5e65d61b..92b16588 100644 --- a/docs/tutorial.md +++ b/docs/tutorial.md @@ -159,7 +159,7 @@ The power of sections really shows, however, when we need to execute a sequence Sections can be nested to an arbitrary depth (limited only by your stack size). Each leaf section (i.e. a section that contains no nested sections) will be executed exactly once, on a separate path of execution from any other leaf section (so no leaf section can interfere with another). A failure in a parent section will prevent nested sections from running - but then that's the idea. -## BDD-Style (Behaviour Driven Development) +## BDD-Style (Behaviour Driven Development) If you name your test cases and sections appropriately you can achieve a BDD-style specification structure. This became such a useful way of working that first class support has been added to Catch. Scenarios can be specified using ```SCENARIO```, ```GIVEN```, ```WHEN``` and ```THEN``` macros, which map on to ```TEST_CASE```s and ```SECTION```s, respectively. For more details see [Test cases and sections](test-cases-and-sections.md).