-
Notifications
You must be signed in to change notification settings - Fork 910
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-test code coverage #10632
Conversation
# Conflicts: # extensions/integration-tests/package.json # extensions/mssql/yarn.lock
# Conflicts: # extensions/machine-learning/package.json
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.
Looks fine from my end. Couple of questions. Looks like some of the steps from the build failed, but probably not related to your changes.
@@ -2,6 +2,186 @@ | |||
# yarn lockfile v1 | |||
|
|||
|
|||
"@babel/code-frame@^7.10.1": |
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.
why are there so many differences in this yarn.lock file
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.
So for some reason the yarn.lock was referencing the 1.0.5 version of vscodetestcover - which was before my big refactor to use the istanbul libs directly. So these changes are from all that
@@ -6,7 +6,7 @@ | |||
import 'mocha'; | |||
import * as vscode from 'vscode'; | |||
import * as azdata from 'azdata'; | |||
import * as mssql from '../../../mssql'; | |||
import * as mssql from '../../../mssql/src/mssql'; |
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.
can you explain this change a bit
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.
This was just being more explicit with the path - but it doesn't need to change (I was changing other things and just didn't revert this). I'll change it back.
Will be following up with adding a way to merge all the coverage reports together for a comprehensive coverage report.
Moved tests under test directory to keep in line with the test folder structure we use across the rest of the product.