The reference implementation for Gherkin has adopted 'Cucumber expressions' which are a type based argument substitution in step definitions, similar to ours but using a different syntax. Ref. https://cucumber.io/docs/cucumber/cucumber-expressions/

We currently allow this transformation in step definitions (ref #863):

@Then I should be a user named :name

In order to increase com

This area of the readme needs some rework, W3C spec is now conformant on most browsers and we should be recommending people use selenium - Just point them to the drivers and use proper browsers. https://github.com/cucumber/godog#testing-browser-interactions

I know a few people said they wanted to help maintain, this would be a good first issue.

Checking the parsing examples from Gherkin, the following fail due to issues with scenario outlines:

• descriptions.feature - the description on the final Example causes a parse error [moved to #154]
• [incomplete_scenario_outline](https://github.com/cucumber/cucumber/blob/master/gherkin/testdata

[x] bug report
[x] feature request

Current behavior
Using a glob pattern eg: test/e2e/feature/**/*.feature to point to sources; runner says the source doesn't exist.

Expected/desired behavior
Ability to use glob pattern to point to sources

ESpec is not fired despite being specified as the testing library in the WhiteBread context file:

mix white_bread.run
loading all contexts from features/contexts/**
** (exit) exited in: GenServer.call(:espec_specs_agent, {:update, #Function<0.60990145/1 in ESpec.add_spec/1>}, 5000)
** (EXIT) no process: the process is not alive or there's no process currently associated with the given n

	И я запоминаю строку "Значение" в переменную "$$ИмяПеременной$$"
	И я запоминаю строку "Значение" в переменную "$$ИмяПеременной$$"

При втором вызове в контексте появляется переменная со значение вместо имени.

p.s. с $ОбычнымКонтекстом$ такая же беда.

I can find lots of code examples on how to use it (in example/) but there are no build system files (CMakeLists.txt) in those directories. Reading the top-level CMakeLists.txt, it sets up the test( file SCENARIO=) command, which seems like a good approach for the tests within this library:

/GUnit/
    example/*.cpp
    test/*.cpp

But more likely a typical app structure wi

Support jUnit XML properties in the already existing extension.
The properties should origin from the Feature Description like:

Feature: XML Properties
    This is arbitrary text and shouldn't be treated as
    a property. Even with a colon in it.

    Property A: foo
    Property B: bla

Also see #387

Let's standardize on what Jasmine does: describe declares a "suite" and it declares a "spec".

This will make it less confusing for future users and contributors, and is especially important for ExampleSpec since that is what people see first when they find Spectrum on GitHub.

To do:

• Read/seach through Spectrum's tests to find usages and mis-usages of "suite", "spec", and "test"
• [

One of the main features of gherkin is the support for writing scenarios and features in your own language. It seems like this project only supports steps written in english.

Please add support for more languages.
A list of translations for the different keywords can be found here:
https://github.com/cucumber/cucumber/blob/master/gherkin/gherkin-languages.json

Relish is closing, according to apiaryio/gavel-spec#57 (comment). Before we have time to tackle apiaryio/gavel-spec#21, we should remove Relish from everywhere, replace it with links to Gherkin files on GitHub, and close the account.

• replace all references to https://relishapp.com/ in gavel-spec docs (README, etc.)
• re

It's time to properly handle the documentation :). This is a summary ticket for all tasks related to the docs update.

• migrate whatever is worth and still true from the wiki to our docs site
• document the new functionality related to interfaces handling
• document the setup with various cloud providers, e.g. SauceLabs, Crossbrowsertesting, etc. (#69)
• running tests in para

Hi,
First of all, thank you for this project. I find gherkin very useful and a linter is always a good safeguard.

When using keyword feature, we are supposed to be able to indent like following example described in the reference documentation :

Feature: Guess the word

  # The first example has two steps
  Scenario: Maker starts a 

FF - Today at 12:46 PM

It should perhaps be pointed out that the breath counter is synchronised, while the breath rate is intended to be personal.
I understood that the sensei so to speak would guide the group to breathe in a synchronised manner, since I didn't see a clear distinction between the act of breathing and the act of counting.

Do you want to request a feature or report a bug?
More of a Readme update.

What is the current behavior?
The readme has some installation examples, they all have defineSupportCode, a function that was deprecated in cucumber in version 4.0.0 (Cucumber Changelog)

**If the current behavior is a bug, p

In order to extend tomato functionality, it would be nice to have a concrete example of how to write a custom resource.