Convert Autosave conflict tests using AutoSaveConflictTestTrait into functional test to test caching

Created on 10 July 2025, 4 days ago

Overview

In πŸ› Add rudimentary conflict prevention to the Config Auto-save end-point Active updated the auto-save conflict detect test coverage to also cover Javascript components and Asset libraries. There were caching implications to the change in that issue because autoSaveStartingPoint value is created by the loading the save entity.

Unfortunately, the test coverage is still kernel tests which can't properly test caching, see \Drupal\Core\PageCache\RequestPolicy\CommandLineOrUnsafeMethod

Proposed resolution

We need to convert all the tests that use \Drupal\Tests\experience_builder\Kernel\AutoSave\AutoSaveConflictTestTrait into functional tests to test caching

User interface changes

πŸ“Œ Task
Status

Active

Version

0.0

Component

Auto-save

Created by

πŸ‡ΊπŸ‡ΈUnited States tedbow Ithaca, NY, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024