Pre-check

• [x ] I'm aware that I can edit the docs and submit a pull request

Describe the improvement

I'd like to report

• Unclear documentation
• A typo
• Missing documentation
• Other

Description of the improvement / report
Auto Completion page suggests ho

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

I came across https://astexplorer.net/ today and thought this could be an excellent debugging and education tool for Gherkin.

How to add support for new parser is well documented.

JavaDoc is the most easilly available source of information for developers using Cucumber. Each class annotated with @API should have a brief explanation what the class is for and how it should be used.

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.

Summary

The documentation "activate_announcer_on_command_failure" is not helpful for users as it misses information a

Please take look at ReusingStepDefinitions.md and notice that in the suggested example (second large code block) there is a variable myAccount. However this variable does not exist at this point in time. It seems this shared-steps was created as a result of hasty refactoring, and I see no way to link myAcco

[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

This is the default in Cucumber JS since v2.0.0-rc.3 (2016-12-19)

It is even documented as a test : https://github.com/cucumber/cucumber-js/blob/master/features/strict_mode.feature

However currently protractor-cucumber-framework set it has false by default

Описание ошибки

Failed
Отчет.АнализЗамеровПроизводительности.ФормаНастроек - <АдминистраторМСК>
Overview History Retries
{ОбщаяФорма.ФормаНастроекОтчета.Форма(34)}: Не передан служебный параметр "НастройкиОтчета".
	ВызватьИсключение НСтр("ru = 'Не передан служебный параметр ""НастройкиОтчета"".'");
Categories: Product defects
Severity: normal
Duration:  205ms
Description
ТестДол

Can the bars in features, tags, steps summary pages be made clickable so the link opens to the details page directly.
So it goes from pages/tag-summary.html to pages/tag-scenarios/tag_TagOver.html when the TagOver bar is clicked.
Saves the time for scrolling and searching for the desired tag, feature or step in the section below.

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

My favorite feature of behave, a Python port of cucumber, is the capture group highlighting. This is helpful for two reasons:

• It helps validate complex regexes during step development
• It informs someone viewing the output which portion of the step is dynamic and could be modified

this is valid ruby, should not be flagged

Hi!
I wanted to write test using regex.
When I looked in doc I found:

there is element ":elementName" with regex ":matcher"

https://thesoftwarehouse.github.io/Kakunin/docs/steps-elements#there-is-no-element-elementname-with-regex-matcher

Unfortunately this scenario doesn't work:

   ? Then there is element "body" with regex "<matcher>"
       Undefined. Implement with the fo