When running multiple test suites in parallel, the exports must currently be identical for all mocked-module declarations. E.g. you cannot have import mockFoo from 'mock{all,the,things}:foo'; in one test file and import mockFoo from 'mock{other,things}:foo'; in another test file.
Due to Web Test Runner's underlying architecture, each it test runs in isolation. However, some state related to the mocking is present in the host Node process. The implementation should be updated to ensure that one test file's mocks cannot impact another test file's mocks.
When running multiple test suites in parallel, the exports must currently be identical for all mocked-module declarations. E.g. you cannot have
import mockFoo from 'mock{all,the,things}:foo';in one test file andimport mockFoo from 'mock{other,things}:foo';in another test file.Due to Web Test Runner's underlying architecture, each
ittest runs in isolation. However, some state related to the mocking is present in the host Node process. The implementation should be updated to ensure that one test file's mocks cannot impact another test file's mocks.