Group: GitHub Lemonlion

Sort by:Popular▼

✓Popular✓Newest

Kronikol4J core — the stable tracking seam (data model, logger, context, correlation, registry, constants). Zero runtime dependencies beyond the JDK.

Kronikol4J run lifecycle — collects scenario results, finalizes the report at end-of-run, and (across forked JVMs) emits/merges report fragments. Mode detection via the kronikol.run.dir property (plan §5).

Kronikol4J report assembly — turns tracked logs + scenarios into an interactive browser-rendered HTML report (and the mergeable JSON fragment). Embeds the diagram data map for client-side PlantUML rendering.

Kronikol4J diagram pipeline — turns tracked logs into PlantUML DSL text (sequence/component), plus the PlantUML text encoder and report data models. Pure logic, no runtime dependencies (the canonical JSON note formatter is hand-rolled for parity, ...

Kronikol4J HTTP tracker — records outgoing HTTP exchanges as tracked interactions (the LogPair auto-resolve ingestion pattern). Provides a recorder that OkHttp/WebClient/RestTemplate interceptors delegate to.

Kronikol4J servlet filter — server-side Layer-1 test-identity resolution (plan §7): reads the test-identity headers off an incoming request and scopes them for request handling, so tracking inside the system-under-test attributes to the calling test. ...

Kronikol4J Spring integration (plan §7) — a RestTemplate ClientHttpRequestInterceptor that records outgoing HTTP exchanges (delegating to the HTTP recorder). Targets jakarta/Spring 6 (compileOnly); the user brings Spring.

Kronikol4J assertion tracking Tier 1 (plan §3.9) — zero bytecode weaving. Captures assertion outcomes via AssertJ's native hooks: per-failure soft-assertion collection and the global description consumer.

Kronikol4J assertion tracking Tier 2 (plan §3.9) — a ByteBuddy agent that instruments AssertJ to auto-capture each assertion's actual + expected values AND its source expression, with NO wrapper and NO .as(). The full-fidelity capture .NET achieves ...

Kronikol4J AWS adapters — records S3, DynamoDB, SQS and SNS operations as tracked interactions. The recorders are pure (no AWS SDK dependency); an AWS SDK ExecutionInterceptor delegates to them.

Kronikol4J Azure adapters — records Cosmos DB, Blob Storage and Service Bus operations as tracked interactions. Pure recorders (no Azure SDK dependency); an Azure SDK pipeline policy delegates to them.

Kronikol4J Cassandra tracker — records CQL operations as tracked interactions (Cassandra category -> database shape). A RequestTracker/wrapper delegates to it.

Kronikol4J CLI — the `merge` command (the 'Merging Parallel Reports' feature, plan §5.5): reads enriched JSON fragments from sharded CI runners and combines them into one HTML report. Distribute as a runnable jar / Gradle goal.

Kronikol4J Cucumber adapter — a Cucumber EventListener that scopes scenario identity and maps Given/When/Then to Setup/Action phases (exercising TestPhaseContext). The user brings Cucumber (compileOnly).

Kronikol4J Elasticsearch / OpenSearch tracker — records search/index operations as tracked interactions (Elasticsearch category -> database shape). A client wrapper delegates to it.

Kronikol4J Google Cloud adapters — records BigQuery, Pub/Sub and Cloud Storage operations as tracked interactions. Pure recorders (no GCP SDK dependency).

Kronikol4J gRPC adapter — a ClientInterceptor that records gRPC calls as tracked interactions (nearly 1:1 with the .NET gRPC interceptors). The recorder is testable without gRPC; the interceptor compiles against grpc-api (compileOnly).

Kronikol4J JDBC tracker — records SQL executions as tracked interactions (the direct log() construction pattern, the .NET EF Core interceptor equivalent). One JDBC-level tracker covers every relational database (plan §2).

Kronikol4J JUnit 5 adapter — an Extension that scopes test identity (with mandatory clearing) and records scenario results, plus a ServiceLoader-registered LauncherSessionListener that finalizes the report once per JVM (plan §5.4).

Kronikol4J messaging tracker — records publish/consume as fire-and-forget Event interactions (MessageQueue category -> queue shape). Kafka/JMS/RabbitMQ wrappers delegate to it; producers/consumers also propagate identity via the kronikol-test-* ...