Skip to main content

Integration Test Tracker

This page tracks the release-critical integration suites that back the 1.1.0 line.

Current Priority

Current branch focus:

  • feature/37-regional-rulepacks-big-7

Primary release claim:

  • Spring Prism can ship modular regional rulepacks without breaking 1.x locale fallback behavior

Active Suites

SuiteLocationPurposeStatus
Redis multi-node suiteprism-integration-testsCross-node restore, TTL expiry, Redis outage handling, noisy LLM restore, large-payload coverageGreen
Optional NLP extension suiteprism-integration-testsDisabled-by-default behavior, heuristic opt-in redaction, false-positive guardrails on technical textGreen
Regional rulepack suiteprism-integration-testsLocale selection for RO, US, PL, NL, GB, FR, and DE plus runtime snapshot totalsGreen
Spring AI WireMock suiteprism-spring-aiAdvisor interception and OpenAI-compatible restore behaviorGreen
Starter auto-configuration suiteprism-spring-boot-starterRedis vault selection, readiness, actuator metricsGreen
Example app smoke suitesprism-examplesReal application boot and wiring coverageGreen

Redis Multi-Node Scenarios

ScenarioStatus
Determinism and regression baselinePassing
Cross-node token restorePassing
TTL expiryPassing
Secret mismatch safetyPassing
Large-payload flowPassing
RAG-style dense payload flowPassing in suite design, local Docker execution required
Redis outage handlingPassing

Optional NLP Scenarios

ScenarioStatus
Disabled by defaultPassing
Heuristic person-name redactionPassing
Person-name restore after LLM responsePassing
Technical phrase false-positive guardrailPassing
Hybrid backend startup validation without modelPassing

Validation Commands

Focused suite:

mvn -pl prism-integration-tests -am test -Dtest=RedisMultiNodeIntegrationTest -Dsurefire.failIfNoSpecifiedTests=false
mvn -pl prism-integration-tests -am test -Dtest=OptionalNlpExtensionIntegrationTest -Dsurefire.failIfNoSpecifiedTests=false

Full reactor validation:

mvn verify

Notes

  • prism-integration-tests is a test-only module and is configured with maven.deploy.skip=true.
  • Redis outage coverage currently validates fail-closed behavior by asserting that tokenize and restore operations fail in a controlled way while Redis is unavailable.
  • Large-context and optional NLP work in v1.1.0 should keep this suite updated whenever runtime behavior changes in a way that affects end-to-end sanitization or restoration.