feat: #3613916 Extend the Varbase functional testing suite for the Educare site template

Rajab Natshahrequested to merge
issue/educare-3613916:3613916-extend-testing-suite into 1.0.x

Issue: https://www.drupal.org/project/educare/issues/3613916

Extends the suite added in !13 (merged) from 6 feature folders to 11, adding the coverage the Varbase suites have and Educare did not: full CRUD per content type, quality gates, SEO, Canvas editor and permission boundaries.

What this adds

Folder Coverage
01-website-base-requirements front-end pages warm-up, navigation + footer, responsive navigation
02-news, 03-events, 04-programs exposed filters, paging, study levels
07-quality axe-core accessibility, performance budgets, editorial accessibility checker
08-seo metatags
09-editorial create/read/update/delete for News, Event, Program, Utility page, and Media
10-drupal-canvas the shipped Canvas pages open in the Canvas editor
11-permissions anonymous and per-role boundaries

Educare had no project step definitions at all, so this also adds three (educare.steps.js, varbase.steps.js, drupal-canvas.steps.js) plus nine selectors and two media test assets.

Two fixes to existing assertions

tests/features/03-events/03-01-events-listing.feature asserted "Showing 1-12 of 39" and a pinned event title. The events view filters field_when_end_value > now, so both the total and which events land on page one decay with wall-clock time: a demo event ending mid-morning took the total to 38 and dropped that title, turning the suite red on a date rather than on a defect. It now asserts the 1-12 page range and a full page of cards, so a total under 13 still fails, which is the real signal that the demo events have aged out.

The anonymous editoria11y scenario asserted "#ed11y-main-toggle" should not be visible. That selector never exists for anyone (editoria11y 2.4.7 renders its toggle inside a shadow DOM), so it passed vacuously. It now asserts the ed11y-element-panel custom element is not attached, which can actually fail.

Known gaps, tagged @wip

Three scenarios are tagged @wip (CI runs not @wip) rather than dropped or loosened, each with a comment in the feature explaining why:

  • Event Body rich text does not persist when filled through the WYSIWYG step, while a recipe-created demo Event renders its Body fine — a step/widget gap.
  • The Event round trip's UPDATE half does not persist the new title.
  • The Program round trip's UPDATE half does not persist the field_degrees checkboxes. This one may be a real Programs form defect and is worth a look.

Everything else passes. The demo content counts are asserted only where they are genuinely deterministic: 04-01-programs-listing keeps of 12 because that view has no date filter.

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