fix(test): check token expiry inside jwtVerify mock implementation #359
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.
The issue
Inside
session.spec.ts, in the following 7 test cases:We have this code:
The issue is that whether the generated test token is valid or not doesn’t have any impact on the outcome of the test. For example, I can create a valid token by passing
falseas the second argument togenerateTestToken()and the test would still pass. This is because thejwtVerify()mock, instead of checking the expiration of the test token, is hard-coded to throw an “Invalid token” error.The fix
Now, inside the
jwtVerify()mock implementation, I check for the expiry of the test token and throw an "Invalid token" error ONLY when the token is expired.Note: Since the test token is generated with immediate expiry (0 seconds) via the
trueflag, I advance the fake timer by 1 second so the expiration check fails as expected.