Problem/Motivation

The suite checks the content model, but not that an editor can publish an episode and a listener can find and play it.

Proposed resolution

  • New scenarios: editor to reviewer publishing, mp3 upload through the media library, anonymous listener journey, drafts hidden from the listing, search and sitemap, SEO basics, accessibility on the listing and an episode page.
  • Tighten the existing scenarios, add named selectors, tag every scenario, and purge what each scenario creates so the suite re-runs on the same site.
  • Move to @vardot/varbase-e2e ^2.0.7 and its stricter accessibility gate.

Remaining tasks

  • ✅ File an issue
  • ✅ Addition/Change/Update/Fix
  • ❌ Testing to ensure no regression
  • ✅ Automated unit/functional testing coverage
  • ➖ Developer Documentation support
  • ➖ User Guide Documentation support
  • ➖ UX/UI designer responsibilities
  • ➖ Accessibility and Readability
  • ❌ Reviewed by a human
  • ❌ Code review by maintainers
  • ❌ Full testing and approval
  • ❌ Credit contributors
  • ❌ Review with the product owner
  • ❌ Update Release Notes
  • ❌ Release

Release notes snippet

  • task: #3625560 Add usage scenarios to the Varbase functional testing suite and move to varbase-e2e 2.0.7.

AI-Generated: Yes

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

rajab natshah created an issue. See original summary.

rajab natshah’s picture

Issue summary: View changes

rajab natshah’s picture

Status: Active » Needs review

MR !8 ready for review.

  • rajab natshah committed 5f8e6c05 on 1.0.x
    task: #3625560 Add usage scenarios to the Varbase functional testing...
rajab natshah’s picture

Status: Needs review » Fixed
Issue tags: +varbase_podcasts_base-1.0.0

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.