-
Notifications
You must be signed in to change notification settings - Fork 58
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
Add integration tests for build commands #1185
Conversation
48338b6
to
62f0931
Compare
- Validate the workflow of user calling the Swift: Run Build/Clean Build/Debug Build commands. - Ensure Swift: Run Build will not get blocked by pre-set breakpoint. - Ensure Swift: Clean Build will result in a cleaned up .build folder. - Ensure Swift: Debug Build will stop on a breakpoint and resume. Issue: swiftlang#1184
- Added comments for clarification - Added utilities to listen for dap message, this is useful for test synchronization. Code takes inspiration from swiftlang#1126
- Minor cosmetic change to utilies/commands.ts
62f0931
to
240dc39
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
otherwise looks good
const result = vscode.commands.executeCommand(Commands.DEBUG); | ||
expect(result).to.eventually.be.true; | ||
|
||
await bpPromise.then(() => continueSession()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if we're hitting breakpoints, crossing into smoke level, let's create a smoke suite and put that there
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought that's what @slow do right now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
still should split into separate suite. Is it actually slow or just trying to keep out of CI build?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are we trying to achieve to split this into a separate suite? Is it for dependency management?
Given the test run fast and this is a command that should probably always work, I am not sure if we want keep this out of CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will leave this for until long term approach is decided
returned, causing restore of setting being not awaitable - Make makeDebugConfigurations to be awaitable - Change launch to also update the key for ASLR disable settings - Make the test properly set up and reset the settings that update the launch config
Issue: #1184