fix(test): Fixed improper mocking of ioredis resources in unit tests #11
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 discovered after I woke up and saw PR #10 was approved and merged, that the output of the unit test runs included
ioredis
errors where it was attempting to connect to a redis host. I had improperly mocked only the functions I was testing in theRedis
object and not all resources fromioredis
. This fix resolves the issue and the tests still behave as desired.unit.spec.ts
to properly mock allioredis
resources using vitest.