You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like wrapito to be agnostic of the test framework we're using.
🎯 Motivation
Currently this version is only compatible with vitest because we use Vitest's mocking capabilities in order to verify if an endpoint was called, which parameters it was called with, etc.
Although this has worked well so far we shouldn't couple wrapito to any test framework, if possible. So, my suggestion here would be to use something like Tinyspy in order to do the verifications and decouple from vitest | jest.
This will also allow us to have only one version of wrapito.
👀 Example
This shouldn't affect end users since it's only used internally.
The text was updated successfully, but these errors were encountered:
✨ Feature proposal
I would like
wrapito
to be agnostic of the test framework we're using.🎯 Motivation
Currently this version is only compatible with
vitest
because we use Vitest's mocking capabilities in order to verify if an endpoint was called, which parameters it was called with, etc.Although this has worked well so far we shouldn't couple
wrapito
to any test framework, if possible. So, my suggestion here would be to use something like Tinyspy in order to do the verifications and decouple fromvitest | jest
.This will also allow us to have only one version of
wrapito
.👀 Example
This shouldn't affect end users since it's only used internally.
The text was updated successfully, but these errors were encountered: