fix: #3621426 Pin @cucumber/cucumber so the functional test suite can run

Rajab Natshahrequested to merge
issue/varbase_content_base-3621426:3621426-varbase-e2e-2-0-4 into 1.0.x

Makes the Varbase Content Base recipe functional test suite able to start at all, and moves the harness onto ^2.0.4 in the same change.

The breakage this fixes is pre-existing. On an untouched checkout of 1.0.x with the current ^2 constraint, cucumber-js aborts before counting a single scenario:

Error: @cucumber/pretty-formatter does not export a function/class

Issue: https://www.drupal.org/project/varbase_content_base/issues/3621426

Why it was broken

@vardot/varbase-e2e asks for @cucumber/cucumber at *, this project commits no lock file, and it declares no overrides or resolutions. A fresh install therefore resolves cucumber to 13.2.1 while @cucumber/pretty-formatter is still on the 1.0.x line, which is not compatible with it.

Varbase Starter is the control that proves this. Its suite runs, and the only relevant difference is that it pins the pair. These are its pins, and this MR copies them rather than inventing anything.

What changed

  • package.json: pin @cucumber/cucumber to 12.9.0 and @cucumber/pretty-formatter to 1.0.1 in both overrides and resolutions, matching Varbase Starter.
  • package.json: "@vardot/varbase-e2e" from "^2" to "^2.0.4".
  • This project commits no lock file, so package.json is the whole diff.

Test notes

Measured, not inferred. Before: the dry run aborts with the error above, no scenario counted. After: cucumber resolves to 12.9.0 and pretty-formatter to 1.0.1, the harness installs at 2.0.4, and the dry run is 6 scenarios and 26 steps, all skipped — no errors, nothing undefined, nothing ambiguous.

The ^2.0.4 bump rides along on purpose: until the suite can start, a version bump here has no observable effect. 2.0.4 adds access assertions, page title assertions and an HTTP status phrasing, and makes the existing HTTP status step session aware.

AI-Generated: Yes

Checkpoints:

  • File an issue
  • Addition/Change/Update/Fix
  • Testing to ensure no regression
  • Automated unit testing coverage
  • Automated functional testing coverage
  • UX/UI designer responsibilities
  • Readability
  • Accessibility
  • Performance
  • Security
  • Developer Documentation
  • User Guide Documentation
  • Reviewed by human
  • Code review by maintainers
  • Full testing and approval
  • Credit contributors
  • Review with the product owner
  • Release notes snippet
  • Release
Edited by Rajab Natshah

Merge request reports