@sheremet-va I didn't consider that at all because, in that case, shouldn't the beforeEach also be in a different order?
I guess my confusion is that when I think about extending the test, I didn't really associate that extension with other functions.
I do understand that we are extending the "context", but still, it does feel off.

Yes, and it does run before beforeEach, otherwise you wouldn't have access to todos. Try running your reproduction with --disableConsoleIntercept.

I do understand that we are extending the "context", but still, it does feel off.

If you feel like it's off, you can start using test.beforeEach/test.afterEach with the latest beta version.

@sheremet-va I have run the same test with disableConsoleIntercept=true

and still got the same result:

beforeAll
beforeEach
Starting test
done
afterEach
Ending test
afterAll

Hence the reason of my confusion, unless this is a bug?

Just for completeness, this is my vitest.config.ts

import { fileURLToPath } from "node:url";
import { mergeConfig, defineConfig, configDefaults } from "vitest/config";
import viteConfig from "./vite.config";

export default mergeConfig(
  viteConfig,
  defineConfig({
    test: {
      environment: "jsdom",
      exclude: [...configDefaults.exclude, "e2e/**"],
      root: fileURLToPath(new URL("./", import.meta.url)),
      setupFiles: ["./src/__tests__/setup.ts"],
      disableConsoleIntercept: true,
    },
  })
);

Ah, sorry. That does make sense because you are not using todos inside beforeEach, so it is initialised just before the test is running.