Bug: testNamePattern option unnecessarily requires a leading space for an exact match.

[senkenn]

Describe the bug

There is a example test.

it("foo", () => {
  expect(1).toBe(1);
});

We require a leading space for an exact match by testNamePattern.

vitest -t '^ foo$' # '^foo$' skips it.

This is also the same describe name.

On the other hand, Jest can run it by '^foo$'. Is this behavior as expected in Vitest?

Reproduction

1. Create a JavaScript file like the above, and pnpm i -D vitest
2. Run pnpm vitest run -t '^foo$' and get the skipped result.

❯ pnpm vitest run -t '^foo$' 
The CJS build of Vite's Node API is deprecated. See https://vitejs.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated for more details.

 RUN  v2.0.3 /home/foo/bar

 ↓ index.test.js (1) [skipped]
   ↓ foo [skipped]

 Test Files  1 skipped (1)
      Tests  1 skipped (1)
   Start at  01:46:52
   Duration  270ms (transform 21ms, setup 0ms, collect 5ms, tests 0ms, environment 0ms, prepare 78ms)

3. Run pnpm vitest run -t '^ foo$' and get the success result.

❯ pnpm vitest run -t '^ foo$'
The CJS build of Vite's Node API is deprecated. See https://vitejs.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated for more details.

 RUN  v2.0.3 /home/foo/bar

 ✓ index.test.js (1)
   ✓ foo

 Test Files  1 passed (1)
      Tests  1 passed (1)
   Start at  01:50:46
   Duration  266ms (transform 19ms, setup 0ms, collect 5ms, tests 1ms, environment 0ms, prepare 68ms)

System Info

System:
    OS: Linux 6.5 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 5700U with Radeon Graphics
    Memory: 2.68 GB / 14.94 GB
    Container: Yes
    Shell: 5.8.1 - /usr/bin/zsh
  Binaries:
    Node: 20.14.0 - ~/.nvm/versions/node/v20.14.0/bin/node
    Yarn: 1.22.22 - ~/.local/share/pnpm/yarn
    npm: 10.7.0 - ~/.nvm/versions/node/v20.14.0/bin/npm
    pnpm: 9.5.0 - ~/.local/share/pnpm/pnpm
    bun: 1.0.35 - ~/.bun/bin/bun
  Browsers:
    Brave Browser: 126.1.67.123
    Chrome: 126.0.6478.126
  npmPackages:
    vitest: ^2.0.3 => 2.0.3

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.