test: #3639053 Update the webship-js suite for webship-js 2.0.12, with the accounts made by the site build
The webship-js suite moves to webship-js 2.0.12 and the book's corrected practice: the site build makes the accounts, the suite only logs in.
cucumber.jsfrom the webship-js 2.0.12 scaffold, with @webship-js/drupal-core-steps and the users registry: credentials from the environment,CHANGE_MEplaceholders.playwright.config.tsfrom the scaffold.- CI (
webship-js-test): a password per account made inbefore_script, Standard installed with the Webmaster account and the recipe applied, the Content editor and plain accounts created with drush. No password is committed. 01-01-01: the logins only (Then I should be logged in).- Module and content type checks through the pack:
the "webapi" module should be installed,the "Webpage" content type should exist. webship-js^2.0.12,@webship-js/drupal-core-steps^2.2.3, no cucumber-js pin.tests/README.md: the full install from a Webships project to a green run, and the Test users; it no longer gives a committed password. The README and a CI comment describe the Swagger UI library package without naming its vendor.
Verified on a site from drupal/webships_project 12.0.x-dev (Drupal 11.4.12, DDEV, Node.js 24), installed from recipes/webapi_starter as the README says: 15 of 15 scenarios (83 steps) pass, twice in a row; also 15 of 15 on the same codebase installed by the Webships installer with this site template. As the suite was: 15 of 15, with the accounts it made left on the site. yarn test:dry: 0 undefined, 0 ambiguous. ESLint as the eslint job runs it: no error. The changed CI lines checked with gitlab-ci-local (a stub drush): the passwords are made and reach drush.
Issue: https://www.drupal.org/project/webapi_starter/issues/3639053
AI-Generated: Yes (tests updated with Claude Code; 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