-
Notifications
You must be signed in to change notification settings - Fork 53
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
build(tests): type check integration.test.ts #413
Conversation
Looks like jest runs twice, once for *.test.ts, and once for *.test.js. |
@@ -0,0 +1,4 @@ | |||
module.exports = { | |||
testEnvironment: 'node', | |||
testPathIgnorePatterns: [".d.ts", ".js"] |
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.
maybe in a followup PR, should the jest config in package.json be migrated to (another) jest.config.js?
node-client/packages/neovim/package.json
Line 81 in 0640e9b
"jest": { |
nit: seems like eslint doesn't check this file, but probably should:
testPathIgnorePatterns: [".d.ts", ".js"] | |
testPathIgnorePatterns: ['.d.ts', '.js'], |
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.
How about moving the jest.config.js content into packages/integration-tests/package.json for consistency?
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.
Sure that's fine. I have the impression that the .config.js files are the preferred approach these days (at least for eslint), but we will probably remove jest eventually (#333) so doesn't matter for 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.
Great! After this is merged, I'll start working on it. Mocha seems like a good choice.
The unreliable test: emits "disconnect" after quit failed again, can u help me to rerun this job ? @justinmk |
Closes #352.