DongHyeonkaandClaude Opus 5
b2963105a8
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
46 lines
3.5 KiB
Plaintext
46 lines
3.5 KiB
Plaintext
# command: ./gradlew :messaging:messaging-spring-boot-starter:test --rerun-tasks --console=plain
|
|
# revision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
|
|
# exit: 0
|
|
|
|
BUILD SUCCESSFUL in 28s
|
|
49 actionable tasks: 49 executed
|
|
|
|
name="dev.caskeleton.messaging.autoconfigure.BatchPublisherTest" tests="11" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.autoconfigure.BlockingFacadeTest" tests="3" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.autoconfigure.MessagingAutoConfigurationTest" tests="17" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.autoconfigure.MessagingConfigurationBindingTest" tests="10" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.autoconfigure.MessagingEndpointTest" tests="5" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.autoconfigure.MessagingLiveRoundTripQualificationTest" tests="1" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.autoconfigure.MessagingOutboxRelayLifecycleTest" tests="2" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.autoconfigure.MessagingShutdownLifecycleTest" tests="2" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.autoconfigure.MessagingStarterOffContractTest" tests="10" skipped="0" failures="0" errors="0"
|
|
name="dev.caskeleton.messaging.autoconfigure.ReactiveFacadeTest" tests="4" skipped="0" failures="0" errors="0"
|
|
TOTAL tests=65 failures=0 errors=0 skipped=0
|
|
|
|
# ***중요*** MessagingLiveRoundTripQualificationTest 가 skipped=0 으로 실행되어 통과했다.
|
|
# @EnabledIf("dockerAvailable") 조건이 참이었고, apache/kafka:4.1.0 컨테이너가 떴다.
|
|
# 이 테스트가 단언하는 것:
|
|
# 1. MessagingPlatformRootAutoConfiguration 로 컨텍스트가 조립된다 (hasNotFailed)
|
|
# 2. MessagePublisher.publish(...) 의 결과가 PublishCompletion.CONFIRMED 다
|
|
# 3. result.evidence().brokerAccepted() 가 true 다
|
|
# 4. 별도 KafkaConsumer 로 토픽에서 레코드를 읽어낼 수 있다
|
|
#
|
|
# => **발행 경로는 실제 브로커에 대해 종단간 검증된다.** 이 revision, 이 환경에서 직접 확인했다.
|
|
#
|
|
# 단, 4번의 읽기는 플랫폼 컨슈머가 아니라 원시 KafkaConsumer 다.
|
|
# 테스트 주석(:136-138)이 그것을 의도로 명시한다:
|
|
# "bytes left the process and a consumer that shares nothing with the producing code but the
|
|
# topic name read them"
|
|
# 독립성 확보라는 목적에서는 옳다. 동시에 **플랫폼의 소비 경로는 이 검증에 포함되지 않는다**.
|
|
# EVD-316 의 "스타터에 컨슈머 빈이 없다" 와 합치면:
|
|
# 라운드트립 자격 검증이 존재하고 통과하며, 설계상 비-플랫폼 컨슈머를 쓴다.
|
|
|
|
# 테스트가 인용하는 결함 이력 (MessagingLiveRoundTripQualificationTest:40-43)
|
|
# "Every messaging signal in this repository came from a fixture. The legacy adapter's KafkaSender
|
|
# existed only as a test double; the platform's publisher could not be assembled at all, because
|
|
# the starter did not depend on the leaf holding it and the codec registry it needs had no
|
|
# implementation. 'Messaging works' was a statement about hand-rolled fakes."
|
|
# 그리고 :123-129 의 단언 메시지가 네 개의 부재를 나열한다:
|
|
# the starter's dependency on messaging-runtime-core, the codec registry, the declared message
|
|
# contract, and a MessagingRuntime to install
|