Vitest advertises a Jest-compatible API, and it delivers. describe , test , expect , toHaveBeenCalledWith — all identical. Which is why the five things that aren't compatible are so disorienting: the suite mostly runs, and then a handful of files fail for reasons the error messages don't explain.
Source: [Dev.to](https://dev.to/msakai/five-things-that-break-when-you-move-from-jest-to-vitest-3g3p)