IBX-12241: Added Behat coverage for Varnish TTL, stale cache, cache keys and tagging - #85
Open
vidarl wants to merge 2 commits into
Open
IBX-12241: Added Behat coverage for Varnish TTL, stale cache, cache keys and tagging#85vidarl wants to merge 2 commits into
vidarl wants to merge 2 commits into
Conversation
ibexa-workflow-automation-1
Bot
requested review from
Steveb-p,
ViniTou,
alongosz,
barw4,
bnowak,
ciastektk,
konradoboza,
mikadamczyk,
tbialcz and
wiewiurdp
and removed request for
a team
August 11, 2026 08:31
…cache keys and tagging
vidarl
force-pushed
the
IBX-12241-varnish-cache-behat
branch
from
August 12, 2026 06:49
fa2e2ea to
108fbfd
Compare
|
mnocon
approved these changes
Aug 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
The Varnish suites currently assert
x-cache: MISS|HIT, purge-on-edit, ESI embedding andtranslation-aware purging — in other words, whether something is cached.
Nothing covers how long it stays cached, what happens once it expires, what the cache key
is, or which tags go out on the response, even though the shipped VCL has real logic for all four.
This PR adds scenarios for that
For QA:
Run against a Varnish setup with
WEB_HOSTpointing at the Varnish container, setup suite first:vendor/bin/behat --profile=httpCache --suite=setup # rebuild the container cache, then vendor/bin/behat --profile=httpCache --suite=varnish6 vendor/bin/behat --profile=httpCache --suite=varnish7Note that scenarios that assert
MISSfirst need a cold Varnish, the same assumptioncache.featurealready makes. Re-running against a warm cache fails them; restart the Varnish container between
runs.
Documentation: