new feature file

cucumber · Sep 13, 2017 · f7bac5c · f7bac5c
1 parent 97f23cf
commit f7bac5c
Show file tree

Hide file tree

Showing 3 changed files with 85 additions and 72 deletions.
diff --git a/features/specific/boost_specific.feature b/features/specific/boost_specific.feature
@@ -0,0 +1,79 @@
+@boost
+Feature: Check macros used with boost test driver
+
+  This is just a simple feature meant to test boost's 
+  specyfic validation macros interop with cucumber.
+
+  Scenario Outline: <check> macro
+    Given the following feature:
+      """
+      Feature: Feature name
+        Scenario: Scenario name
+          Given a step
+      """
+    And a step definition file with:
+      """
+      #include <boost/test/unit_test.hpp>
+      #include <cucumber-cpp/autodetect.hpp>
+      GIVEN("a step") {
+        <check>(false);
+      }
+      """
+    When Cucumber runs the feature
+    Then the scenario <passes or fails?>
+
+    Examples:
+      | check           | passes or fails? |
+      | BOOST_WARN      | passes           |
+      | BOOST_CHECK     | fails            |
+      | BOOST_REQUIRE   | fails            |
+
+
+  Scenario Outline: <check> macro
+    Given the following feature:
+      """
+      Feature: Feature name
+        Scenario: Scenario name
+          Given a step
+      """
+    And a step definition file with:
+      """
+      #include <boost/test/unit_test.hpp>
+      #include <cucumber-cpp/autodetect.hpp>
+      GIVEN("a step") {
+        <check>(false, "boost message");
+      }
+      """
+    When Cucumber runs the feature
+    Then the scenario <passes or fails?>
+
+    Examples:
+      | check                 | passes or fails?                    |
+      | BOOST_WARN_MESSAGE    | passes                              |
+      | BOOST_CHECK_MESSAGE   | fails with message "boost message"  |
+      | BOOST_REQUIRE_MESSAGE | fails with message "boost message"  |
+
+
+  Scenario Outline: <check> macro
+    Given the following feature:
+      """
+      Feature: Feature name
+        Scenario: Scenario name
+          Given a step
+      """
+    And a step definition file with:
+      """
+      #include <boost/test/unit_test.hpp>
+      #include <cucumber-cpp/autodetect.hpp>
+      GIVEN("a step") {
+        <check>("boost message");
+      }
+      """
+    When Cucumber runs the feature
+    Then the scenario <passes or fails?>
+
+    Examples:
+      | check                 | passes or fails?                    |
+      | BOOST_ERROR           | fails with message "boost message"  |
+      | BOOST_FAIL            | fails with message "boost message"  |
+
diff --git a/features/specific/predicate_message.feature b/features/specific/predicate_message.feature
diff --git a/features/step_definitions/cucumber_cpp_steps.rb b/features/step_definitions/cucumber_cpp_steps.rb
@@ -13,3 +13,9 @@
 Then /^a step definition snippet with (".*") is suggested$/ do |regex_string|
     assert_partial_output("(#{regex_string}) {", all_output)
 end
+
+Then /^the scenario fails with message "([^"]*)"$/ do |message|
+  assert_partial_output(message, all_output)
+  assert_success false
+end
+