diff --git a/plainbook/gherkin.xml b/plainbook/gherkin.xml index 8d0a089..90471fb 100644 --- a/plainbook/gherkin.xml +++ b/plainbook/gherkin.xml @@ -500,7 +500,7 @@ an ‘at’ sign (@) before the tag name. For example:

You can tag a feature or a scenario. Feature tags are automatically inherited by all the enclosed scenarios and scenario outlines. Cucumber also supports some more advanced tag features, such as enforcing the limit on the number of scenarios with a particular tag (useful for work-in-progress) and running scenarios that satisfy a combination of tags. For information on those options, have a look at -the .

+the .

@@ -334,7 +334,7 @@ Before('@killer') do # only before scenarios tagged with @killer end -

For more information on scenario hooks in Ruby, see .

+

For more information on scenario hooks in Ruby, see .

You can define scenario hooks in Java using the @Before and @After annotations. For example:

@@ -365,7 +365,7 @@ and list the relevant tags in the annotation. For example:

} -

For more information on scenario hooks in other JVM languages, see .

+

For more information on scenario hooks in other JVM languages, see .

You can define scenario hooks in .NET using the [Before] and [After] attributes. For example:

@@ -397,7 +397,7 @@ To avoid this problem, mark your scenarios with tags and list the relevant tags

The Ruby version of Cucumber (but not Cuke4Duke and Cuke4Nuke) supports many other types of hooks, such as step hooks (executed before or after each step) and global hooks (executed once before any test runs or after all tests finish). They are defined similarly to the scenario hooks covered in this section. For more information, see -.

+.