Open hi-ogawa opened 2 weeks ago
Conceptually, I don't see why it wouldn't work:
vi.setConfig({ sequence: { concurrent: true } })
describe('suite1') // concurrent
describe('suite2') // concurrent
describe('suite3', { concurrent: false }) // sequential
The question is here, I guess:
describe('suite1', () => {
vi.setConfig({ sequence: { concurrent: true } })
describe('suite2') // should it inherit parent suite options or follow global config?
})
Describe the bug
Docs now mentions it's not supported https://vitest.dev/api/vi.html#vi-setconfig But it's available as typing of
vi.setConfig
. https://github.com/vitest-dev/vitest/blob/2a50464d58e98f58fed513971a570a952081bfef/docs/api/vi.md?plain=1#L977-L980But it might be a regression and possible to make it work again https://github.com/vitest-dev/vitest/pull/6653#issuecomment-2403730192
If not, we should update
RuntimeConfig
to hide it from typing.Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-opxrtz?file=repro.test.ts
(based on tests from https://github.com/vitest-dev/vitest/issues/6652)
System Info
Used Package Manager
npm
Validations