-
Notifications
You must be signed in to change notification settings - Fork 29.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test: Task customization #29442
Comments
This should be a complexity of at least 4. |
I have tested out this scenario. But I think we should have additional test plan items for:
|
Agree with @isidorn on additional plan items for menu, as well as for custom workspace configuration. It would be great to see how current task workflow can be reused in some popular sample projects (e.g. MERN, etc.) @dbaeumer can you explain what is an impact of task execution group property (kind)? If I change kind from build to some other, then I don't see it in |
Agree. That is a good idea: I created #29618 and assigned it to @joaomoreno (thanks for volunteering) and @michelkaporin |
Regarding the group: I should remove clean and rebuildAll for now. If you assign the test group then the task is listed with Run Test Tasks... The reason why this was not on the plan is that it is simply the same as isTestCommand which got deprecated to have more flexibility in the future. |
thanks for explanation @dbaeumer |
Complexity: 3
Tests: #28235
Setup:
Test:
new
: every execution of the task creates a new panel.dedicated
: there is one panel for the task. Every execution uses the same panel and the panel is not reused with other tasks.shared
: the panel is shared with other tasks that are marked as shared.gulp build
task:"group": { "kind": "build", "isPrimary": true }
. Execute Task > Run Build Task... This should execute the gulp build task without showing the quick pick.The text was updated successfully, but these errors were encountered: