To add a collaborator to this project you will need to use the Relish gem to add the collaborator via a terminal command. Soon you'll be able to also add collaborators here!
More about adding a collaboratorWriting good feature tests with aruba to create documentations
You can use Markdown within your feature tests. This is quite good to write a
living documentation.
There are some edge cases where Gherkin and Markdown don't agree. Bullet lists
using * is one example. The * is also an alias for step keywords in
Gherkin. Markdown headers (the kind starting with a #) is another example.
They are parsed as comments by Gherkin. To use either of these, just escape
them with a backslash. Alternatively just use the "-".
You'd write:
- Scenarios
-
- Make tea
-
## Making tea
* Get a pot
* And some hot waterGiven...
This way Gherkin won't recognize these lines as special tokens, and the reporter will render them as Markdown. (The reporter strips away any leading backslashes before handing it off to the Markdown parser). Another option is to use alternative Markdown syntax and omit conflicts and escaping altogether: ```gherkinThis scenario does not have any steps.
- Make tea
-
Making tea
- Get a pot
- And some hot water
Given...
This scenario does not have any steps.
Last published almost 6 years ago by philoserf.