task: #3621367 Update @vardot/varbase-e2e to ^2.0.4

Rajab Natshahrequested to merge
issue/ace_editor-3621367:3621367-varbase-e2e-2-0-4 into 2.0.x

Moves this project's automated functional testing harness from the stale ~2.0.1 pin onto ^2.0.4.

Issue: https://www.drupal.org/project/ace_editor/issues/3621367

What changed

  • package.json: "@vardot/varbase-e2e" from "~2.0.1" to "^2.0.4".
  • No lock file is committed by this project, so that one line is the whole diff.

Nothing else. No step definition, feature file or selector is touched here.

Why

~2.0.1 resolves to at least 2.0.1 and below 2.1.0, so a fresh install today would already fetch 2.0.4. This is a stale pin rather than breakage: it does not express the floor the suite now needs, and an environment that installed at 2.0.1, 2.0.2 or 2.0.3 stays on the old steps.

@vardot/varbase-e2e 2.0.4 adds 17 built-in steps and fixes one. What this project gains:

  • Access assertions, so a scenario can state what a role may and may not reach.
  • Page title assertions.
  • An added HTTP status code phrasing.
  • A fix to the existing HTTP status step. It used to re-request the URL outside the browser, which lost the session cookies and followed redirects, so it asserted the status of a different request than the one under test. It is now session aware.
  • A Drimage Improved step pack, which this project does not use today.

Test notes

On this branch:

node -e "console.log(require('@vardot/varbase-e2e/package.json').version)"   # 2.0.4
npx cucumber-js --dry-run

The dry run is clean across all 20 scenarios and 129 steps, with no ambiguous and no undefined steps. That is the evidence that pulling 2.0.4 introduced no ambiguity in this project: none of the new library steps collide with anything defined locally here.

The browser suites were not run for this change; it alters no step and no scenario.

Several of this project's own custom steps duplicate phrasings that are now under discussion for the library. This merge request deliberately changes only the constraint: no local step definition is removed here.

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