test(geschichte): document FK-load-bearing cleanup order (#805)
All checks were successful
CI / Unit & Component Tests (pull_request) Successful in 4m28s
CI / OCR Service Tests (pull_request) Successful in 25s
CI / Backend Unit Tests (pull_request) Successful in 4m57s
CI / fail2ban Regex (pull_request) Successful in 53s
CI / Semgrep Security Scan (pull_request) Successful in 28s
CI / Compose Bucket Idempotency (pull_request) Successful in 37s
All checks were successful
CI / Unit & Component Tests (pull_request) Successful in 4m28s
CI / OCR Service Tests (pull_request) Successful in 25s
CI / Backend Unit Tests (pull_request) Successful in 4m57s
CI / fail2ban Regex (pull_request) Successful in 53s
CI / Semgrep Security Scan (pull_request) Successful in 28s
CI / Compose Bucket Idempotency (pull_request) Successful in 37s
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 <noreply@anthropic.com>
This commit was merged in pull request #806.
This commit is contained in:
@@ -95,6 +95,8 @@ class JourneyItemDocumentDeleteTest {
|
|||||||
void cleanup() {
|
void cleanup() {
|
||||||
SecurityContextHolder.clearContext();
|
SecurityContextHolder.clearContext();
|
||||||
reset(documentRepository);
|
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();
|
journeyItemRepository.deleteAll();
|
||||||
docRepo.deleteAll();
|
docRepo.deleteAll();
|
||||||
geschichteRepository.deleteAll();
|
geschichteRepository.deleteAll();
|
||||||
|
|||||||
Reference in New Issue
Block a user