[AXON-46] chore: add unit tests for auth strategies #115
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.
What is this?
When working on the other auth stuff, I've come to the point of doing a pretty big change around
strategy.ts
To minimize the risk of breaking thing, I'm first creating a bunch of unit tests for the existing logic with minimal changes.
The original plan was to literally touch nothing and only add tests, however there are some small necessary changes:
strategy.ts
to a separate filestrategyCrypto.ts
- primarily because it caused issues withjest
for some reason@types/jest
version and added@jest/globals
to resolve the weirdit.each
issueDespite lots of logic, these things are effectively data classes, so I'm only testing the happy path to make sure the output doesn't change accidentally down the line
How was this tested
npm run test # OK