The ambiguous explanation of the test.parallelExecutionLimit and the test.parallelExecutionOfExecutableLimit about vscode-catch2-test-adapter HOT 5 CLOSED

Hello,

Sure, let's discuss it. I'm happy if we can improve this.

Let me ask you a question just to make sure we have the same understanding on some basics.

What is a test and what is an executable and what is the relationship between them for you?

from vscode-catch2-test-adapter.

Hi.

I am a GoogleTest user. So,

• Test: A unit test.
• Executables: An executable file on Windows or Linux.

In my case, an executable file contains multiple unit tests.

from vscode-catch2-test-adapter.

test.parallelExecutionLimit: Maximizes the number of the parallel test executions.

Maximum number of parallel executions of the same test executable. This does not further distinguish between different test cases or permutations / iterations of the same test case.

Limit this if you have resources which are instantiable only a limited number of times per test executable.

Warning: There is no concept of resource groups spanning multiple executables!

test.parallelExecutionOfExecutableLimit: Maximizes the number of the parallel execution of executables.

(Global) total number of parallel executions of any test executable.

This is the number of processes which will be running concurrently at peak.

Additional processes will only be spawned when both the total number of concurrent processes is below test.parallelExecutionOfExecutableLimit and the number of concurrent processes spawned from the target executable is under test.parallelExecutionLimit.

from vscode-catch2-test-adapter.

Thank you very much. This is clear and easy to understand.

from vscode-catch2-test-adapter.

This is not correct. Ah, I definitely should clear this up..

test.parallelExecutionLimit

Maximum parallel run of tasks. Tasks are 'running a set of tests', 'test executable discovery' and 'reload of the executable's test list'. NOTE: If your executables depend on the same resource exclusively then this could cause a problem.

test.parallelExecutionOfExecutableLimit

Maximum number of execution of the same executable. With this config it can be allowed that one executable is running at the same time as multiple processes and those processes 'running a set of tests' parallel. Useful if one executable has a lot of tests which can be run parallel. It won't have effect unless the test.parallelExecutionLimit is adjusted too. To enable this just for specific executables use the testMate.cpp.test.advancedExecutables -> parallelizationLimit. NOTE: if your test cases depend on the same resource exclusively then this could cause a problem.

I hope it's clear now. I will update the docs

from vscode-catch2-test-adapter.