Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

3.0.7 breaks cucumberJS step definitions #156

Copy link
Copy link
@ealmiladi

Description

@ealmiladi
Issue body actions

3.0.7 that was released two days ago broke our CucumberJS integration at our company. While we're not exactly sure what might be broken, all of our cucumber step definitions are resolving as undefined.

E.g.

import { Given } from '@cucumber/cucumber';

Given('I have {int} cucumbers in my belly', function (cucumberCount) {
  assert.equal(this.responseStatus, cucumberCount)
});

When attaching the step definitions to the cucumber CLI runner and executing a test, the test runner is no longer recognizing these step definitions on v 3.0.7.

We had to pin 3.0.4 under the resolutions block of package.json in order to circumvent >3.0.7 and resolve the issue. Many of our dependencies rely on subdependencies that include this project and are now resolving to the 3.0.7 release which includes either a bug or breaking changes.

rohitpratapitm

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.