test(persistence): Scan.contentSha256 in Test-Fixture#5
Merged
Conversation
ProductRepositoryIntegrationsTest und AiEmbeddingPgvectorTest sind jetzt gruen, aber AssessmentImmutableTest scheitert am naechsten NOT-NULL auf Scan.contentSha256 (Pflichtfeld seit der Content-Hash-Migration). Cve.kevListed bleibt unberuehrt: dort setzt @PrePersist implizit FALSE, wenn null. CVM-62 https://claude.ai/code/session_014NNjRKw5bDqRffqCUGe8ud
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
2 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.
Warum
Im main-Lauf nach PR #4 ist
cvm-persistenceweiter rot, aber an einer anderen Stelle:AssessmentImmutableTest.bereiteAssessmentVor:94scheitert am NOT-NULL-ConstraintScan.contentSha256.ProductRepositoryIntegrationsTestundAiEmbeddingPgvectorTestsind grün, also wirkt die tenantId-Korrektur.ProductRepositoryIntegrationsTest-Hibernate-Inserts sind im Log sichtbar.Fix
Ein zusaetzliches Feld auf dem Scan-Fixture-Builder in
AssessmentImmutableTest:NOT-NULL-Audit der restlichen Fixture-Entities ergab keine weiteren Luecken: Environment, Component, ComponentOccurrence, Finding, Assessment, ProductVersion sind bereits vollstaendig.
Cve.kevListedist NOT NULL, aber die Entity hat ein@PrePersist, das aufFALSEfaellt, wenn null - kein Eingriff noetig.Erwartung
Nach Merge: cvm-persistence komplett gruen, dann laufen cvm-application, cvm-integration, cvm-ai-services, cvm-api, cvm-app und cvm-architecture-tests endlich durch. Mit
--fail-at-endsehen wir in einem Lauf alle ggf. noch vorhandenen Failures.https://claude.ai/code/session_014NNjRKw5bDqRffqCUGe8ud
Generated by Claude Code