Add tests for extractor#50
Open
IITI-tushar wants to merge 1 commit into
Open
Conversation
Signed-off-by: Tushar Saxena <019saxenatushar@gmail.com>
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.
This pull request adds comprehensive unit tests for the
ExtractorChainfunctionality in thepkg/attestation/extractor_test.gofile. The new tests verify the registration and retrieval of extractors, supported types, registration of custom extractors, and the behavior of extracting files from attestations—including deduplication and filtering.Key additions and improvements:
ExtractorChain registration and retrieval:
material,command-run,product) are registered and retrievable, and that unknown types are not registered.Supported types:
SupportedTypes()returns the expected set of extractor types.File extraction behavior:
ExtractAll()to check deduplication of file paths, correct application of type filters, and correct invocation count of each extractor.