fix: #3625420 Stop asserting a fixed card count on the last events page
Issue: https://www.drupal.org/i/3625420
Changes
03-03-events-filters-and-paging.feature asserted the "events cards" should have a count of 12 on page 2. Page 2 is the last page, so its count is total - 12, which is content volume, not pager configuration, and the scenario says it does not test that.
The events view filters field_when_end_value > now, and the recipe ships 40 events with fixed timestamps, so the total falls on its own as those dates pass. One event ended at 1790258400 (24 Sep 2026 14:00 UTC), taking the listing from 24 to 23. Page 2 then has 11 cards and the assertion fails.
Dropped that assertion and asserted the pagination instead. Page 1 still asserts 12, which is the page size. The Showing 13-N of N range already proves the pager carried on.
Testing
03-events on a fresh Drupal CMS install with the listing at 23 events, the state that fails today: 11 scenarios, 11 passed.
This is what turns 1.0.x red right now, and it blocks !77 (merged). The next event expires on 29 September.
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