configuring h2 tests with production auth interceptor to safely enable refactor #138
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.
Summary
problem: I cannot refactor the interceptor here (safely): #133 because it doesn't have test coverage.
why?
we have two types of methods to enable authentication in unittests:
in addition, I will be refactoring the interceptor in a different PR. this PR requires proper testing to prevent regressions in the logic.
So to fix, we need a unittest framework that allows us to:
Changes
Testing Done
since this only changed config for H2 unittests, all h2 unittests are passing including the new unittest i added.
proving that the production auth interceptor configuration results in desired outcome from unittests:
Additional Information