chore: add test afterAll timeout to wait for message processing

[SirSimon04]

Have you...

• Added relevant entry to the change log?

[hyperspace-insights]

The PR adds afterAll(() => (cds as any).flush()) to every inner describe block, but an identical afterAll already exists at the outer describe level — this is a meaningful duplication that risks flushing shared CDS state mid-suite, potentially corrupting isolation between subsequent inner suites. The single outer-level cleanup (already present and matching the pattern in programmaticApproach.test.ts) is sufficient; all six newly added inner afterAll blocks should be removed.

PR Bot Information

Version: 1.19.15 | 📖 Documentation | 🚨 Create Incident | 💬 Feedback

• LLM: anthropic--claude-4.6-sonnet
• Correlation ID: a6ba57b0-2dd5-11f1-9976-f874771d4ccc
• Event Trigger: pull_request.opened
• File Content Strategy: Full file content

[hyperspace-insights]

Summary

The following content is AI-generated and provides a summary of the pull request:

---

Add afterAll Timeout to Ensure Message Processing Completion in Tests

Chore

🔧 Added a 5-second delay in afterAll hooks across all test files to ensure pending outbox messages are fully processed before test teardown completes.

Changes

All modified test files follow the same pattern — a await new Promise((resolve) => setTimeout(resolve, 5000)) delay is appended after (cds as any).flush() in the afterAll hook to allow asynchronous message processing to finish gracefully.

• tests/hybrid/annotationApproach.test.ts: Added a new afterAll block with cds.flush() and a 5-second timeout.
• tests/hybrid/programmaticApproach.test.ts: Added a new afterAll block with cds.flush() and a 5-second timeout.
• tests/integration/annotations/businessKey.test.ts: Added 5-second delay after cds.flush() in existing afterAll.
• tests/integration/annotations/customEvents.test.ts: Added 5-second delay after cds.flush() in existing afterAll.
• tests/integration/annotations/deleteMultiEvent.test.ts: Added 5-second delay after cds.flush() in existing afterAll.
• tests/integration/annotations/draftAnnotation.test.ts: Added 5-second delay after cds.flush() in existing afterAll.
• tests/integration/annotations/isolated.test.ts: Added 5-second delay after cds.flush() in existing afterAll.
• tests/integration/annotations/lifeCycleAnnotation.test.ts: Added 5-second delay after cds.flush() in existing afterAll.
• tests/integration/annotations/multipleStartAnnotations.test.ts: Added 5-second delay after cds.flush() in existing afterAll.
• tests/integration/annotations/processStart-input.test.ts: Added 5-second delay after cds.flush() in existing afterAll.
• tests/integration/annotations/wildcardEvents.test.ts: Added 5-second delay after cds.flush() in existing afterAll.
• tests/integration/genericProgrammaticApproach.test.ts: Added 5-second delay after cds.flush() in existing afterAll.
• tests/integration/programmaticApproach.test.ts: Added 5-second delay after cds.flush() in existing afterAll.

---

• 🔄 Regenerate and Update Summary
• ✏️ Insert as PR Description (deletes this comment)
• 🗑️ Delete comment

PR Bot Information

Version: 1.20.0 | 📖 Documentation | 🚨 Create Incident | 💬 Feedback

• Output Template: Default Template
• Correlation ID: f8334f00-2e8b-11f1-8f7d-1eb808c4982c
• Event Trigger: pull_request.ready_for_review
• Summary Prompt: Default Prompt
• LLM: anthropic--claude-4.6-sonnet
• File Content Strategy: Full file content

---

💌 Have ideas or want to contribute? Create an issue and share your thoughts with us!
📑 Check out the documentation for more information.
📬 Subscribe to the Hyperspace PR Bot DL to get the latest announcements and pilot features!

Made with ❤️ by Hyperspace.

[hyperspace-insights]

The PR adds an identical afterAll teardown block to 13 test files — calling cds.flush() followed by a hard-coded 5-second setTimeout. While the intent (letting async message processing finish before the process exits) is sound, the implementation has a maintainability concern: the magic number 5000 is duplicated across all files and the overall approach is non-deterministic. A single shared utility (or at least a named constant) would make the timeout easier to adjust and signal intent more clearly. No functional correctness bugs were found beyond that concern.

PR Bot Information

Version: 1.20.0 | 📖 Documentation | 🚨 Create Incident | 💬 Feedback

• Event Trigger: pull_request.ready_for_review
• LLM: anthropic--claude-4.6-sonnet
• File Content Strategy: Full file content
• Correlation ID: f8334f00-2e8b-11f1-8f7d-1eb808c4982c

[Kronprinz03]

LGTM