From f65296172fc13103eaf81313ba4dc568e195ff1a Mon Sep 17 00:00:00 2001 From: Marcel Date: Thu, 11 Jun 2026 19:23:33 +0200 Subject: [PATCH] test(geschichte): document FK-load-bearing cleanup order (#805) Adds a comment on the @AfterEach deletion sequence explaining that journey_items must be removed before their referenced documents and geschichten. Addresses @sara review on PR #806. Co-Authored-By: Claude Opus 4.8 --- .../geschichte/journeyitem/JourneyItemDocumentDeleteTest.java | 2 ++ 1 file changed, 2 insertions(+) diff --git a/backend/src/test/java/org/raddatz/familienarchiv/geschichte/journeyitem/JourneyItemDocumentDeleteTest.java b/backend/src/test/java/org/raddatz/familienarchiv/geschichte/journeyitem/JourneyItemDocumentDeleteTest.java index b23ef447..f1319cb2 100644 --- a/backend/src/test/java/org/raddatz/familienarchiv/geschichte/journeyitem/JourneyItemDocumentDeleteTest.java +++ b/backend/src/test/java/org/raddatz/familienarchiv/geschichte/journeyitem/JourneyItemDocumentDeleteTest.java @@ -95,6 +95,8 @@ class JourneyItemDocumentDeleteTest { void cleanup() { SecurityContextHolder.clearContext(); reset(documentRepository); + // Deletion order is FK-load-bearing: journey_items reference both documents + // and geschichten, so children must be removed before their parents. journeyItemRepository.deleteAll(); docRepo.deleteAll(); geschichteRepository.deleteAll();