Repository navigation
refactor: improve runtime log visibility across transports and matchers - #69
Merged
Merged
Conversation
Contributor
📋 Unreleased Changelog Preview
ChangelogAll notable changes to this project will be documented in this file. [Unreleased]✨ Features
Generated by git-cliff 🔄 Run #189 · Sun, 18 Oct 2026 14:27:08 GMT |
…Exception' Co-authored-by: Copilot Autofix powered by AI <223894421+github-code-quality[bot]@users.noreply.github.com>
10 of 17 tasks
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
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.
📝 Summary
Improve runtime log visibility and consistency across
ktestify-coreandktestify-cucumberso users can follow every phase of scenario execution, transport operations, and record assertions without log spam:ktestify-core):INFO: partition assignment, offset seeks per partition, polling start/attempt counts, deduplication skips/clears, Schema Registry subject/version lookups, and matcher execution/verdicts.INFOwhile keeping full produced/consumed payloads atDEBUG.ERRORlogs on produce and synchronous request failures.ktestify-core):INFOpass andERRORfailure/diff logs acrossFieldsRecordMatcher,XmlRecordMatcher,XPathRecordMatcher,AvroFieldsRecordMatcher, andAvroFileRecordMatcher.XMLUtilsfromDEBUGtoERRORon mismatch.ERRORlogs inAvroUtilswhen probing candidate elements in unordered arrays andLAZYbatch comparisons (doesAvroRecordsSmartMatchesQuietly/doesAvroRecordsSmartMatchesWithExclusionsQuietly).INFOinDynamicVariableProcessor.ktestify-cucumber):BackgroundStepDefinitionresource registrations (namespaces, topics with resolved namespaced names, assets directory, schemas) toINFO.INFOprogress logs (including row-by-row tracking for multi-row DataTables, batch parameters, and watcher checks) andERRORfailure logs inActionStepDefinition,ValidationStepDefinition,ProducerValidationService, andConsumerValidationService.Closes #
🔄 Type of change
fix): non-breaking change that fixes an issuefeat): non-breaking change that adds functionality!): changes existing behaviour, public API, Gherkin steps or config keysrefactor): no functional changeperf)docs)build(deps))ci/build): workflows,pom.xml, tooling✅ Checklist
Code
mvn spotless:check(runmvn spotless:applyto fix it and add the Apache 2.0 headers)Tests
mvn verifypasses locally, and JaCoCo line coverage stays ≥ 70 %Testcontainers-based tests are isolated and clean up after themselvesCompatibility & docs
New or changed HOCON keys have a default inreference.confand a documented env-var overrideNew or changed Gherkin steps are documented, with an example scenarioNew SPI implementations are registered inMETA-INF/services/