support parallel test execution #260
Conversation
|
I couldn't help myself and just added test lookup functionality (right click on test -> Go to Test). This leads to the source file that a test exe is built from. This only works for simple tests that are made up of one source file, but that should be the majority of tests. |
Jannik2099
force-pushed
the
parallel_tests
branch
from
1523925 to
b94ce5d
Compare
|
@Jannik2099 do you think this PR is ready to go? Sorry it's taken me a long time to get to it |
Jannik2099
force-pushed
the
parallel_tests
branch
3 times, most recently
from
d70915c to
ecdb6f2
Compare
|
Sorry for the delay, I managed to break my finger which made interfacing with a keyboard... difficult. I addressed all your points. |
|
I guess this slipped my mind when cutting the new release. Is there any way you could rebase on main, so I can get this for 1.28? |
Signed-off-by: Jannik Glückert <[email protected]>
Signed-off-by: Jannik Glückert <[email protected]>
Signed-off-by: Jannik Glückert <[email protected]>
Signed-off-by: Jannik Glückert <[email protected]>
this is required when targets exist twice, e.g. due to subprojects Signed-off-by: Jannik Glückert <[email protected]>
Signed-off-by: Jannik Glückert <[email protected]>
Jannik2099
force-pushed
the
parallel_tests
branch
from
ecdb6f2 to
504f766
Compare
|
No worries, I rebased & tested that things still work as expected. |
|
Thanks for your work. Will review next week. |
This adds parallel test execution through the vscode TestController API. Sequential tests
test(..., is_parallel = false)are respected.Parallelism is set to the number of CPUs, if desired I could also add a config option.
I also fixed output formatting of test failures as
vscode.TestRun.appendOutputalways expects CLRF.