plugins { id 'ca.grpc-platform-module' } // Certification. The Stable plan splits this across four modules (core / in-process / netty / // fault); this repository already expresses "these two runs are not the same kind of evidence" with // strict test lanes rather than with module boundaries, so the four become four lanes over one // leaf (adaptation design §2). A lane that discovers nothing fails, and the three hermetic lanes // reuse a result only when their classes and their lane policy are unchanged — the performance lane // never does. That is the property the split was protecting. strictTestLanes { lane('grpcInProcessContractTest') { tag = 'grpc-inprocess' description = 'In-process contract lane: adapter, interceptor order, status, idempotency ' + 'replay. Never HTTP/2, TLS or transport-limit evidence.' } lane('grpcNettyContractTest') { tag = 'grpc-netty' description = 'Real Netty lane: HTTP/2 on an ephemeral socket, TLS/mTLS, metadata and ' + 'message hard limits, GOAWAY, keepalive and drain.' } lane('grpcFaultTest') { tag = 'grpc-fault' description = 'Fault-injection lane: connection loss at each evidence boundary, and the ' + 'classifier that refuses to infer NOT_SENT from an unobserved state.' } lane('grpcPerformanceTest') { performance() tag = 'grpc-performance' description = 'Performance lane: unary latency percentiles, channel stream saturation, ' + 'executor saturation and drain budget against a recorded baseline.' } } // The performance lane is excluded from the default `test` task. It measures a running server // under load, so it is not in the pull-request or release gate; it runs in the optional build's // `performanceCheck`, which integration-main.yml's performance-check job runs on main and nightly. tasks.named('test') { useJUnitPlatform { excludeTags 'grpc-performance' } } dependencies { api project(':grpc:grpc-core-api') api project(':grpc:grpc-runtime') api project(':grpc:grpc-observability') api project(':grpc:grpc-operation-ledger-jpa') api "io.grpc:grpc-api" api "io.grpc:grpc-stub" // The transports the lanes stand on. In-process is fast contract evidence; Netty is the only // transport this platform certifies, and the lane separation is what keeps them distinguishable. implementation "io.grpc:grpc-inprocess" implementation "io.grpc:grpc-netty-shaded" }