Mrc-5952 vitest pt 1 #219
Mrc-5952 vitest pt 1 #219
Conversation
| vi.mock("plotly.js-basic-dist-min", () => { | ||
| return { | ||
| default: undefined, | ||
| update: undefined | ||
| } | ||
| }); | ||
| vi.mock("../../../../src/components/help/MarkdownItImport.ts", () => { | ||
| class MarkDownItClass { | ||
| constructor() { | ||
| return { | ||
| use: vi.fn().mockReturnValue({ | ||
| renderer: { rules: {} }, | ||
| render: vi.fn() | ||
| }) | ||
| } | ||
| } | ||
| }; | ||
| return { | ||
| default: { | ||
| default: MarkDownItClass | ||
| } | ||
| } | ||
| }); |
There was a problem hiding this comment.
If some of these bits are going to pop up several times, I wonder if it would be worth importing them from a shared module?
There was a problem hiding this comment.
thats a good idea im not sure if you actually can even extract out vi.mocks, they seem to care about hoisting and not capturing stuff from the env and so on but i think there must be some functionality in vitest! i have made a ticket: https://mrc-ide.myjetbrains.com/youtrack/issue/mrc-5980/vi.mock-in-shared-module will do it in a future pr
i did these PRs after they all started passing, will see it passing fairly soon! |
part 1 for the vitest upgrade, some main changes to be aware of that youll be seeing in the following PRs:
vi.mockis very similar tojest.mockbut you do have to mock everything the component uses explicitly so if you importupdatefunction fromplotly.js-basic-minthen you have to explicitly state it as undefined even if you dont use it in the test soupdate: undefinedvi.mockand use them later in your file to see how many times theyve been called for example then you must usevi.hoistedto create your mocked functions and these will be available invi.mockand the rest of your testsdonecallbacks have been deprecated for a while, so replacingsetTimeoutwith await/async