Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Test: multi root debug #31396

Closed
3 tasks done
isidorn opened this issue Jul 25, 2017 · 0 comments
Closed
3 tasks done

Test: multi root debug #31396

isidorn opened this issue Jul 25, 2017 · 0 comments
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues testplan-item
Milestone
July 2017

Comments

@isidorn
Copy link
Contributor

isidorn commented Jul 25, 2017 •
edited by michelkaporin
Loading

Refs: #29245

Complexity: 4

We have made debug multi root aware. First quickly verify you can debug a no folder workspace and a single folder workspace as before.

Open a multi root workspace where there are multiple launch.json files, verify:

  • All configurations from every workspace are shown
  • It is possible to add configuraitons to each of the launch.json from the dropdown
  • Clicking on the configure action opens the appropriate launch.json
  • Variables in the launch.json get resolved depending on where the launch.json is located, for example ${workspaceRoot} resolves to the fs path of the root containg that launch.json
  • Be creative and check if the UI behaves as one would expect
@isidorn isidorn added debug Debug viewlet, configurations, breakpoints, adapter issues testplan-item labels Jul 25, 2017
@isidorn isidorn added this to the July 2017 milestone Jul 25, 2017
This was referenced Jul 27, 2017
Closed
Closed
This was referenced Jul 27, 2017
Closed
Closed
Closed
@jrieken jrieken removed their assignment Jul 27, 2017
@egamma egamma removed their assignment Jul 27, 2017
This was referenced Jul 27, 2017
Closed
Closed
Closed
@michelkaporin michelkaporin mentioned this issue Jul 27, 2017
Closed
@michelkaporin michelkaporin removed their assignment Jul 27, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues testplan-item
Projects
None yet
Milestone
July 2017
Development

No branches or pull requests
4 participants
@egamma @jrieken @isidorn @michelkaporin