Conversation
…merValidationService
Contributor
📋 Unreleased Changelog Preview
ChangelogAll notable changes to this project will be documented in this file. [Unreleased]✨ Features
Generated by git-cliff 🔄 Run #131 · Thu, 01 Oct 2026 19:52:18 GMT |
Contributor
✅ Test Results
|
This branch has not been deployed
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.
📝 Description
Extends the
KeyMatchStrategyfeature (introduced inktestify-core) into the Cucumber DataTable layer, allowing users to specify an optionalkeyMatchStrategycolumn in any step that acceptsexpectedRecordKey.What changed:
DATA_TABLE_KEY_MATCH_STRATEGY = "keyMatchStrategy"constant toDataTableUtils.getKeyMatchStrategy(Map<String, String> row)private static helper toConsumerValidationServicethat parses the DataTable column value viaKeyMatchStrategy.fromString()(defaults toEXACTwhen absent or blank)..keyMatchStrategy(getKeyMatchStrategy(row))into all 9ConsumerContext.builder()calls and 3MatchContext.builder()calls that setexpectedRecordKey.getKeyMatchStrategy().key-matchers.feature,key-filtering.feature,watcher.feature).step-reference.mdx,built-in-matchers.mdx,core-concepts.mdx, andktestify-cucumber/README.md.Why:
Users have record keys that are dynamically generated (UUIDs, prefixed keys, hash-based keys). Exact match is too restrictive for these use cases. The
keyMatchStrategycolumn lets users choosecontains,starts_with,ends_with, orregexmatching at both the fetch-time pre-filter and the assertion-time matcher layers.Resolves #46
🔄 Type of Change
✅ Pre-Merge Checklist
Code Quality
mvn spotless:check)Tests
mvn verify)Licensing
🧪 How to Test Locally