Issue Task Resolved

#110649Install tool presets e2e test leaves the cache preset switched

Stefan Bürk 09/07/26, 22:52 updated 09/14/26, 09:50

Description

Summary

The Playwright install tool e2e spec runs as a single serial block with two
retries. When one test of that block fails, the whole block is repeated from
its first test, against the same TYPO3 instance and the same database. The
test “configuration presets works” switches the cache preset and leaves it
switched, which makes the earlier test “analyze database structure works“
fail on every retry.

Details

An instance is set up with the default cache configuration, where the caches
hash, pages and rootline use the database backend. Their tables cache_hash,
cache_pages and cache_rootline, together with the matching tag tables, are
therefore part of the expected database schema and are created during setup.

The presets test switches the cache preset to “Database” and then to “File”,
where it stops. Activating a preset only writes the configuration, and TYPO3
deliberately never drops tables on its own. With the “File” preset active,
the six cache tables are no longer part of the expected schema, so the
database analyzer offers them for removal as unused tables.

The test “analyze database structure works” asserts that the schema is up to
date and runs before the presets test. It passes on the first attempt. As
soon as any test of the block fails and the block is retried, it runs against
the state the previous attempt left behind, finds the six unused tables and
fails. Everything after it in the block is skipped, so one unrelated failure
turns the whole spec red.

This was observed in a pipeline where a proxy error on an unrelated Install
Tool card triggered the retry, and both further attempts then failed on the
schema assertion instead of on the original problem.

Steps to reproduce

  1. Run the install tool e2e spec once.
  2. Run it a second time against the same instance.
  3. “analyze database structure works” now fails, the expected callout for an
    up to date schema is missing and the analyzer lists the six cache tables
    under “Remove tables (rename with prefix)”.

Expected behavior

Every test of the spec restores the state it changed, so that a retry starts
from the same state as the first attempt.

Actual behavior

The cache preset stays on “File” and the cache tables are left behind as
unused tables for every test that runs afterwards.

Reviews 2

History 15

  1. Stefan Bürk commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-09-14T09:50:11+00:00" > 09/14/26, 09:50 </span>

    Applied in changeset commit:d62c074814793c54158fc3d206c9eabf7e4e8b21.