-
Notifications
You must be signed in to change notification settings - Fork 245
chore: bump the major version we run unit tests on in ci #6378
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -252,8 +252,10 @@ describe('connectMongoClient', function () { | |
| expect(error).to.be.instanceOf(Error); | ||
|
|
||
| // propagates the tunnel error | ||
| expect(error.message).to.match( | ||
| /(All configured authentication methods failed|ENOTFOUND compass-tests\.fakehost\.localhost)/ | ||
| // NOTE: this heavily depends on which server version we're running on | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. do we have to test for a specific message? can't we just confirm an error?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't know. I didn't write the original test and I don't want to unnecessarily change the intention.
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. or, if we want to test the propagation, is there a way to mock the server error?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, but this file is an integration test, not a unit test. |
||
| const message = error.errors ? error.errors[0].message : error.message; | ||
| expect(message).to.match( | ||
| /(All configured authentication methods failed|ENOTFOUND compass-tests\.fakehost\.localhost)|ECONNREFUSED 127.0.0.1:22/ | ||
| ); | ||
|
|
||
| for (let i = 0; i < 10; i++) { | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
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'm thinking we should probably not set this here and use it in print-compass-env.js and then somehow rather fill in a default if nothing is set in the compass tests. That would be the only way to have a consistent default locally and in CI because we don't use this file when just doing
npm testlocally.