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

test: fix tests that check error messages #3727

Closed
wants to merge 1 commit into from
Closed

Conversation

cjihrig
Copy link
Contributor

@cjihrig cjihrig commented Nov 9, 2015

20285ad changed the format of error messages throughout lib. However, the tests were not updated to reflect these changes. This commit makes those changes.

20285ad changed the format
of error messages throughout lib. However, the tests were not
updated to reflect these changes. This commit makes those
changes.
@Fishrock123
Copy link
Contributor

@silverwind @micnic please be sure to always run the tests before landing. :D

@silverwind
Copy link
Contributor

Thanks @cjihrig for picking the slack! LGTM, verified locally as CI seems to still be down.

@@ -566,7 +566,7 @@ posix.extname = function(path) {
posix.format = function(pathObject) {
if (pathObject === null || typeof pathObject !== 'object') {
throw new TypeError(
"Parameter 'pathObject' must be an object, not " + typeof pathObject
'Parameter "pathObject" must be an object, not ' + typeof pathObject
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this one missed in the original commit, by the way?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. And it made one of the path tests a pain to fix.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@micnic want to do a second pass if there are more errors that were missed, like this one?

@silverwind silverwind added the test Issues and PRs related to the tests. label Nov 9, 2015
@jbergstroem
Copy link
Member

LGTM

1 similar comment
@jasnell
Copy link
Member

jasnell commented Nov 10, 2015

LGTM


assert.throws(function() {
new Buffer(null);
}, /must start with number, buffer, array or string/);
}, /must start with number, buffer, array or string/i);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why ignore case is necessary in these two places?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The error string is 'Must start with number, buffer, array or string'.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then, why not fix the string itself? That would be better, right?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll do that on the landing.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made the regex case insensitive because if that were already the case, this test wouldn't have broken at all.

@silverwind silverwind self-assigned this Nov 10, 2015
cjihrig added a commit that referenced this pull request Nov 10, 2015
20285ad changed the format
of error messages throughout lib. However, the tests were not
updated to reflect these changes. This commit makes those
changes.

PR-URL: #3727
Reviewed-By: Roman Reiss <[email protected]>
Reviewed-By: Johan Bergström <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@silverwind
Copy link
Contributor

Landed in 2c33819 with the suggested regex change. master is green again, sorry for the trouble.

I'll have a look at the remaining error messages in case more were missed.

@silverwind silverwind closed this Nov 10, 2015
@cjihrig cjihrig deleted the errs branch November 10, 2015 15:44
@jasnell
Copy link
Member

jasnell commented Nov 10, 2015

@cjihrig ... should this be looked at for v4.x?

@cjihrig
Copy link
Contributor Author

cjihrig commented Nov 10, 2015

I don't think so. The PR that updated the error messages was deemed not LTS (#3374).

@silverwind silverwind added the semver-major PRs that contain breaking changes and should be released in the next major version. label Nov 12, 2015
@silverwind
Copy link
Contributor

This depends on #3374, which makes it a semver-major.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver-major PRs that contain breaking changes and should be released in the next major version. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants