Enhance recog verify to report an untested parameter as a failure#19
Merged
mkienow-r7 merged 2 commits intorapid7:masterfrom Feb 16, 2022
Merged
Conversation
gschneider-r7
approved these changes
Feb 15, 2022
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
Enhances
com.rapid7.recog.verify.RecogVerifierto report an untested parameter as a failure instead of a warning. This creates feature parity with changes introduced in rapid7/recog#405.Motivation and Context
Ensure all fingerprints have examples that fully verify all capture group parameters.
How Has This Been Tested?
mvn clean installbin/recog_verifytool with output fromcom.rapid7.recog.verify.RecogVerifierTypes of changes
Checklist: