|
| 1 | +# Task Metadata |
| 2 | + |
| 3 | +::: warning |
| 4 | +Vitest exposes experimental private API. Breaking changes might not follow semver, please pin Vitest's version when using it. |
| 5 | +::: |
| 6 | + |
| 7 | +If you are developing a custom reporter or using Vitest Node.js API, you might find it useful to pass data from tests that are being executed in various contexts to your reporter or custom Vitest handler. |
| 8 | + |
| 9 | +To accomplish this, relying on the [test context](/guide/test-context) is not feasible since it cannot be serialized. However, with Vitest, you can utilize the `meta` property available on every task (suite or test) to share data between your tests and the Node.js process. It's important to note that this communication is one-way only, as the `meta` property can only be modified from within the test context. Any changes made within the Node.js context will not be visible in your tests. |
| 10 | + |
| 11 | +You can populate `meta` property on test context or inside `beforeAll`/`afterAll` hooks for suite tasks. |
| 12 | + |
| 13 | +```ts |
| 14 | +afterAll((suite) => { |
| 15 | + suite.meta.done = true |
| 16 | +}) |
| 17 | + |
| 18 | +test('custom', ({ task }) => { |
| 19 | + task.meta.custom = 'some-custom-handler' |
| 20 | +}) |
| 21 | +``` |
| 22 | + |
| 23 | +Once a test is completed, Vitest will send a task including the result and `meta` to the Node.js process using RPC. To intercept and process this task, you can utilize the `onTaskUpdate` method available in your reporter implementation: |
| 24 | + |
| 25 | +```ts |
| 26 | +// custom-reporter.js |
| 27 | +export default { |
| 28 | + // you can intercept packs if needed |
| 29 | + onTaskUpdate(packs) { |
| 30 | + const [id, result, meta] = packs[0] |
| 31 | + }, |
| 32 | + // meta is located on every task inside "onFinished" |
| 33 | + onFinished(files) { |
| 34 | + files[0].meta.done === true |
| 35 | + files[0].tasks[0].meta.custom === 'some-custom-handler' |
| 36 | + } |
| 37 | +} |
| 38 | +``` |
| 39 | + |
| 40 | +::: warning |
| 41 | +Vitest can send several tasks at the same time if several tests are completed in a short period of time. |
| 42 | +::: |
| 43 | + |
| 44 | +::: danger BEWARE |
| 45 | +Vitest uses different methods to communicate with the Node.js process. |
| 46 | + |
| 47 | +- If Vitest runs tests inside worker threads, it will send data via [message port](https://developer.mozilla.org/en-US/docs/Web/API/MessagePort) |
| 48 | +- If Vitest uses child process, the data will be send as a serialized Buffer via [`process.send`](https://nodejs.org/api/process.html#processsendmessage-sendhandle-options-callback) API |
| 49 | +- If Vitest run tests in the browser, the data will be stringified using [flatted](https://www.npmjs.com/package/flatted) package |
| 50 | + |
| 51 | +The general rule of thumb is that you can send almost anything, except for functions, Promises, regexp (`v8.stringify` cannot serialize it, but you can send a string version and parse it in the Node.js process yourself), and other non-serializable data, but you can have cyclic references inside. |
| 52 | + |
| 53 | +Also, make sure you serialize [Error properties](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm#error_types) before you set them. |
| 54 | +::: |
| 55 | + |
| 56 | +You can also get this information from Vitest state when tests finished running: |
| 57 | + |
| 58 | +```ts |
| 59 | +const vitest = await createVitest('test') |
| 60 | +await vitest.start() |
| 61 | +vitest.state.getFiles()[0].meta.done === true |
| 62 | +vitest.state.getFiles()[0].tasks[0].meta.custom === 'some-custom-handler' |
| 63 | +``` |
| 64 | + |
| 65 | +It's also possible to extend type definitions when using TypeScript: |
| 66 | + |
| 67 | +```ts |
| 68 | +declare module 'vitest' { |
| 69 | + interface TaskMeta { |
| 70 | + done?: boolean |
| 71 | + custom?: string |
| 72 | + } |
| 73 | +} |
| 74 | +``` |
0 commit comments