task: #3636726 Use @webship-js/drupal-core-steps 2.1 for the webship-js suite and refresh the dependencies

Rajab Natshahrequested to merge
3636726-drupal-core-steps into 1.0.x

Summary

The Webship Portal functional tests (webship-js, Cucumber) now have the public step pack @webship-js/drupal-core-steps (^2.1.0) behind them, so the shared Drupal steps (login by handle, the testing users, named pages, messages, listings, the editor, the media library, access control, site structure) are maintained in the pack, and a test:dry script resolves every step of every scenario without a browser.

Issue: https://www.drupal.org/node/3636726

Changes

  • package.json: adds @webship-js/drupal-core-steps ^2.1.0 to the devDependencies (webship-js stays on ^2.0.6, the pack's peer range) and the test:dry script (cucumber-js --dry-run).
  • cucumber.js: adds the pack's step glob between the webship-js glob and the project's own, and the users registry in the pack's shape (username, email, password, roles, isAdmin) for Webmaster, Content editor and Authenticated user, which the pack's login by handle and I add the testing users read.

This project's own steps (the one-time login by role, and the navigation, landmark, layout and edit-form checks) do not repeat any sentence of the pack, so none is removed. Its pipeline installs Drupal from the recipe (the recipe job) and does not run the browser suite, so no CI job changes here. Node 24 and DRUPAL_CORE: '11.4.x-dev' were already in place.

Test notes

Dry run (cucumber-js --config cucumber.js --dry-run) on Node 24.22.2 from a clean install of this branch, with no lock file: webship-js 2.0.6, @webship-js/drupal-core-steps 2.1.0 and @cucumber/cucumber 12.9.0 resolve, and the run covers 70 scenarios and 507 steps, with none undefined and none ambiguous.

AI-Generated: Yes (configuration and step cleanup; reviewed by Rajab Natshah.)

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