Metadata based filtering for test #1364
Merged
Conversation
This file contains 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
… class and add tests for the same
…accept list of filters
…are two many scenarios, the filter can work seamlessly
…and scenario filtering
joelrosario
requested changes
Oct 19, 2024
core/src/main/kotlin/io/specmatic/core/filters/ScenarioFilterTags.kt
Outdated
Show resolved
Hide resolved
…TATUS-CODE to STATUS
joelrosario
approved these changes
Oct 21, 2024
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.
What:
Add ability to filter tests based on the metadata of a certain test.
Add --filter and --filterNot argument in TestCommand to use these filters.
The filters follow a specific syntax which can be understood using
specmatic test --helpcommand.Why:
The existing --filterName and --filterNotName were serving the purpose of filtering tests to an extent but potentially that algorithm is not scalable when it comes to evolving the filtering mechanism and making it more scalable.
Hence, this metadata based filtering is introduced. This is a first cut of it.
Checklist: