features/modeling/scenario_modeling.feature in cucumber_analytics-1.1.1 vs features/modeling/scenario_modeling.feature in cucumber_analytics-1.2.0

- old
+ new

@@ -8,10 +8,11 @@ 2. the scenario's description 3. the scenario's steps 4. the scenario's tags 5. the scenario's applied tags 6. the scenario's source line + 7. the scenario's raw element Background: Test file setup. Given the following feature file: """ @@ -29,10 +30,14 @@ Then a verification step """ And parameter delimiters of "*" and "*" When the file is read + + Scenario: The raw scenario element is modeled. + Then the test correctly stores its underlying implementation + Scenario: The scenario source line is modeled. Then the test is found to have the following properties: | source_line | 6 | Scenario: The scenario name is modeled. @@ -60,10 +65,10 @@ | @a_feature_level_tag | Scenario Outline: Scenario models pass all other specifications Exact specifications detailing the API for Scenario models. Given that there are "<additional specifications>" detailing models - When the corresponding unit tests are run + When the corresponding specifications are run Then all of those specifications are met Examples: | additional specifications | | scenario_unit_spec.rb | | scenario_integration_spec.rb |