Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat!: support multiple parallel child_process #3925

Merged
merged 3 commits into from
Sep 27, 2023
Merged

feat!: support multiple parallel child_process #3925

merged 3 commits into from
Sep 27, 2023

Commits on Sep 14, 2023

  1. feat!: vi.useFakeTimers() to not mock nextTick by default 

    BREAKING CHANGE: `vi.useFakeTimers()` does not mock `nextTick` by default
anymore. It can still be mocked when explicitly specified as:
`vi.useFakeTimers({ toFake: ['nextTick'] })`.
    @AriPerkkio
    AriPerkkio committed Sep 14, 2023
    Configuration menu
    Copy the full SHA
    edaf9e7 View commit details
    Browse the repository at this point in the history

  2. fix!: do not support process.nextTick mocking when --no-threads 

    BREAKING CHANGES: `vi.useFakeTimers({ toFake: ['nextTick'] })` is no longer
supported when running Vitest in `node:child_process`. This has been
broken for a while and has provided flaky tests. Use `--threads` when
you need to mock `process.nextTick`.
    @AriPerkkio
    AriPerkkio committed Sep 14, 2023
    Configuration menu
    Copy the full SHA
    5d8e695 View commit details
    Browse the repository at this point in the history

  3. feat!: support multiple parallel child_process 

    BREAKING CHANGES: `--no-threads` no longer runs tests in the same test
context. Tests are now isolated in separate processes similar to how
`--threads` does with `worker_threads`.
    @AriPerkkio
    AriPerkkio committed Sep 14, 2023
    Configuration menu
    Copy the full SHA
    e05d466 View commit details
    Browse the repository at this point in the history