Add CustomExecution2 test and make start fire after onDidOpenTerminal #77839
Conversation
extensions/vscode-api-tests/src/singlefolder-tests/workspace.tasks.test.ts
Show resolved
Hide resolved
| let result: vscode.Task[] = []; | ||
| let kind: CustomTestingTaskDefinition = { | ||
| type: taskType, | ||
| customProp1: 'testing task one' |
There was a problem hiding this comment.
It would be great if the test code could demonstrate the use of the value of 'customProp1'.
When I used this in my project, I ended up creating some wrapper classes around the use of virtual terminal process and custom executions so I could get the custom execution data (the properties) back into the execution of the extension code in a seemingly clean way.
When the code is all in one test like this, the "capturing" works just fine, but when you do things like put your task definition in one file, execution of the code in another, etc. it becomes a bit cumbersome.
I can point you to what I ended up doing if you want.
There was a problem hiding this comment.
Would this be as easy as just adding an assertion somewhere?
Part of #70978
cc @GabeDeBacker