AFTER hook executed at beginning of next scenario about cucumber-cpp HOT 3 CLOSED

The fix for the AFTER hook ordering is simple. Just needed to execute the AFTER hooks prior to purging the context.

Although, this uncovered another issue, which is more intricate. The hooks are not wrapped by an exception trap like the steps are, and they don't have the ability to return an InvokeResult, like the steps do. I would need some help on making that happen.

BTW, this is a great framework! Just needs a little polish. We are getting geared up to use it extensively for ATDD for a massive Qt C++ application. ;)

Thanks in advance for you help! See my AFTER hook execution fix below:

--- a/src/CukeCommands.cpp
+++ b/src/CukeCommands.cpp
@@ -14,8 +14,8 @@ void CukeCommands::beginScenario(const TagExpression::tag_list *tags) {
 }
 void CukeCommands::endScenario() {
-    contextManager.purgeContexts();
     hookRegistrar.execAfterHooks(currentScenario.get());
+    contextManager.purgeContexts();
     currentScenario.reset();
 }

from cucumber-cpp.

Yes, that was my guess as soon as I saw that a new context was being created. I'll look into it on the weekend. Feel free to submit a pull request if you can make your wayin thequite messy tests (started a refactoring with mocks as part of feature #31). Thanks for your help and interest :-)

from cucumber-cpp.

Leaving it open despite pull #43 as a reminder that it needs to be tested.

from cucumber-cpp.