-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor and improve UT for PoP token verifier #371
Refactor and improve UT for PoP token verifier #371
Conversation
6a7bdb8
to
05c80e7
Compare
05c80e7
to
fa6bda0
Compare
Make sure to fix the DCO check: |
3ecdb81
to
6637f73
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM, this is really good improvment.
I added comment about structure.
@weinong are you able to trigger BUILD to validates the UT on this PR please ? |
@nehaPrakash98 please check the DCO |
Signed-off-by: Neha Prakash <nehaprakash@microsoft.com>
…d comments for all test cases in pop_tokenverifier_test Signed-off-by: Neha Prakash <nehaprakash@microsoft.com>
… helper file pop_tokenverifier_test_utils.go, refactored test cases to use a table driven approach Signed-off-by: Neha Prakash <nehaprakash@microsoft.com>
b3b3e56
to
00571c8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Previous test coverage was ~80%
Current test coverage is 91.5%