Skip to content

[dev] terminalContrib unit tests fail when run together in isolation #252921

@tmm1

Description

@tmm1

I have been experimenting with running tests in parallel

mocha itself has a parallel mode, but it's only suitable for nodejs tests

A similar technique can be emulated by splitting tests and spawning off multiple test runners. i added a simple patch that can be used as so:

scripts/test.sh --testSplit 2/2

However, I am seeing failures when running specific portions of the test suite.

With #253049 running the command above I see:

  1) TerminalLinkParsing
       "before each" hook in "TerminalLinkParsing":


      + expected - actual


  Error: done() called multiple times in hook <TerminalLinkParsing "before each" hook in "TerminalLinkParsing"> of file vs/workbench/contrib/terminalContrib/links/test/browser/terminalLinkParsing.test; in addition, done() received error: AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:

  2 !== 0

cc @joaomoreno who did some similar work in #241847

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions