Add verification of results via regexp#37
Closed
dvalinrh wants to merge 4 commits into
Closed
Conversation
kdvalin
requested changes
Aug 12, 2025
| %_header | ||
| # connection:TPM | ||
| %_multiples | ||
| [[1-9]][[0-9]]{0,}:[1-9][0-9\.]{1,}$ |
Contributor
Author
|
Will be using python and json instead of regexp. |
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
2 participants
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
This adds the required files and hooks into the wrapper for verification of the test results via regexp.
Mapping results to regexp
Typical results
# connection:TPM
10:421331
20:566553
40:535533
Regexp file contents
%_header
# connection:TPM
%_multiples
[[:digit:]][[:digit:]]{0,}:[1-9][0-9.]{1,}:1$
%_header: Indicates the next line is a header that we need to match.
Field 1: %_iteration means we expect to find anumerical value
Field 2: We expect to find a non zero numerical value.
Before/After Comparison
Before change: Failures will occur on validation
After change: Passes when it should, fails when it should.
Clerical Stuff
This closes #34
Mention the JIRA ticket of the issue, this helps keep
everything together so we can find this PR easily.
Relates to JIRA: RPOPC-422
Testing
Running the wrapper (modifying the regexps to force failures)
Verified test fails when it has bad data
Verified test passes when we have good data.