fix tests that fail for the wrong reasons #45
Merged
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.
I noticed that the test
assertJwtEndpointWithNoKeyThrows()
was taking10 seconds to run so I took a look into why that was.
The test method has
@Test(expected=Exception.class)
but the exceptionthat is thrown is different than the one that the test is expected - the
test was throwing a SocketTimeoutException after 10 seconds (which is
the OkHttpClient's default read timeout setting) because there was no
mock requests enqueued in the mock web server.
I refactored these tests to use
assertThrows
instead to assert againstthe details of the thrown Exceptions, and also fixed what seems like a
bug in the
getAuthorizationHeader
method - if the client has anaccessToken, it will be used as the header, even if the request path is
one that needs a private-key-signed JWT token.