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.

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

Merged
merged 2 commits into from
Oct 10, 2024
Merged

Conversation

gjf7
Copy link
Contributor

@gjf7 gjf7 commented Oct 10, 2024

Closes #352.

@gjf7
Copy link
Contributor Author

gjf7 commented Oct 10, 2024

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"]
Copy link
Member

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?

nit: seems like eslint doesn't check this file, but probably should:

Suggested change
testPathIgnorePatterns: [".d.ts", ".js"]
testPathIgnorePatterns: ['.d.ts', '.js'],

Copy link
Contributor Author

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?

Copy link
Member

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 :)

Copy link
Contributor Author

@gjf7 gjf7 Oct 10, 2024

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.

@gjf7
Copy link
Contributor Author

gjf7 commented Oct 10, 2024

The unreliable test: emits "disconnect" after quit failed again, can u help me to rerun this job ? @justinmk

@justinmk justinmk merged commit e28b0c6 into neovim:master Oct 10, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

build: enable full typescript checking of test files
2 participants