Unexpected Double Quotes Appended to Gherkin Step Outputs

[ThomasSanson]

Dear CodeceptJS Team,

I hope this message finds you well. I am reaching out to report an unusual behaviour I've encountered while using CodeceptJS, specifically related to the execution of Gherkin steps. Despite following the documentation closely and setting up a project according to the Quick Start guide, including the initialization for Gherkin, I have observed that each step's output in the console is unexpectedly appended with two double quotes ("").

This peculiarity arises regardless of whether the configuration is set up in JavaScript or TypeScript. It's important to note that this issue seems to manifest exclusively within the context of Gherkin; traditional step definitions do not exhibit this same behaviour.

To provide you with a more concrete example, here is the output I've encountered:

gitpod@xxx:/workspace/test$ npx codeceptjs init
gitpod@xxx:/workspace/test$ npx codeceptjs gherkin:init
gitpod@xxx:/workspace/test$ npx codeceptjs run --colors --steps --verbose
***************************************
nodeInfo:  20.5.1
osInfo:  Linux 6.1 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
cpuInfo:  (16) x64 AMD EPYC 7B13
chromeInfo:  Not Found
edgeInfo:  "N/A"
firefoxInfo:  undefined
safariInfo:  N/A
If you need more detailed info, just run this: npx codeceptjs info
***************************************
CodeceptJS v3.5.13 #StandWithUkraine
Using test root "/workspace/docker/tests/test"
Helpers: 
Plugins: screenshotOnFail

Business rules --
  In order to achieve my goals
  As a persona
  I want to be able to interact with a system
    [1]  Starting recording promises
    Timeouts: 
  do something
   Given I have a defined step ""
  ✔ OK in 13ms

feat1 --
      Timeouts: 
  test something
  ✔ OK in 1ms


  OK  | 2 passed   // 20ms

As illustrated, each gherkin step is followed by an unwarranted pair of double quotes. I've conducted a thorough review of my code, configurations, and the relevant sections of the CodeceptJS documentation to identify any potential misconfigurations or errors on my part, to no avail.

I would greatly appreciate your assistance in understanding the source of this issue. I am curious whether this is a known bug, a side effect of a specific configuration, or perhaps an oversight in my setup process.

For reference, I have attempted both JavaScript and TypeScript configurations, strictly adhering to the guidelines provided in the official documentation. This issue has been consistent across both setups, but only when employing Gherkin for defining tests.

Thank you for your time and assistance. I am looking forward to your guidance on how to resolve this anomaly.

Best regards,

[github-actions]

This issue is stale because it has been open for 90 days with no activity.