Skip to content

Use the result type 'ambiguous' for ambiguous step matches.#1815

Open
brasmusson wants to merge 4 commits intomainfrom
feature/ambiguous-result-type
Open

Use the result type 'ambiguous' for ambiguous step matches.#1815
brasmusson wants to merge 4 commits intomainfrom
feature/ambiguous-result-type

Conversation

@brasmusson
Copy link
Contributor

@brasmusson brasmusson commented Jan 6, 2026

Description

Cucumber-Messages has a separate test step result status 'AMBIGUOUS', therefore cucumber-ruby should use the test result type 'ambiguous' for ambiguous step matches.

This is specifically needed for cck v22 conformance where examples with ambiguous step matches are included (#1806).

Requires cucumber-ruby-core#311

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds new behaviour)
  • If your change may impact future contributors, explain it here, and remember to update README.md and CONTRIBUTING.md accordingly.

Please add an entry to the relevant section of CHANGELOG.md as part of this pull request.

Checklist:

Your PR is ready for review once the following checklist is
complete. You can also add some checks if you want to.

  • Tests have been added for any changes to behaviour of the code
  • New and existing tests are passing locally and on CI
  • bundle exec rubocop reports no offenses
  • RDoc comments have been updated
  • CHANGELOG.md has been updated

Cucumber-Messages has a separate test step result status 'AMBIGUOUS',
therefore cucumber-ruby should use the test result type 'ambiguous'
for ambiguous step matches.
* Use unskippable actions for ambiguous steps so they are identified
  also after failing steps or in dru run mode.
Copy link
Contributor

@luke-hill luke-hill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

5/7 files reviewed and approved. 2 files not yet looked at.

In terms of CI this failure looks related to your PR Bjorn

@luke-hill
Copy link
Contributor

We probably also want to pin core to have a minimum version of the last released (When I get around to it)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants