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: Add tests for add/remove header after sent. #8682

Closed
wants to merge 5 commits into from

Conversation

niklasi
Copy link
Contributor

@niklasi niklasi commented Sep 21, 2016

Checklist
  • tests and/or benchmarks are included
  • commit message follows commit guidelines
Affected core subsystem(s)

test, http

Description of change

This change adds tests to make sure an Error is thrown if a header
is added or removed after they are sent.

This change adds tests to make sure an Error is thrown if a header
is added or removed after they are sent.
@nodejs-github-bot nodejs-github-bot added the test Issues and PRs related to the tests. label Sep 21, 2016
@mscdex mscdex added the http Issues or PRs related to the http subsystem. label Sep 21, 2016
server.listen(common.PORT, () => {
http.get({port: server.address().port}, () => {
server.close()
});
Copy link
Member

Choose a reason for hiding this comment

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

I would listen in the 0 port so it picks a random port

Copy link
Contributor

Choose a reason for hiding this comment

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

Agreed. s/common.PORT/0/

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok, I will fix that. Just a question about it... In the guide for how to write tests it is mentioned that you should "always use common.PORT instead of an arbitrary value as it allows to run tests in parallel safely". It doesn't mention that you can use port 0 as well. If it is preferable to use port 0 than maybe the guide should be updated? Or did I misunderstand the guide?

Copy link
Member

Choose a reason for hiding this comment

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

No, you're right. The guide was written just before changing the policy regarding the port. It should be updated to reflect this change.

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 have updated the PR with 0 as port number now. Thanks for the feedback.

server.listen(common.PORT, () => {
http.get({port: server.address().port}, () => {
server.close()
});
Copy link
Member

Choose a reason for hiding this comment

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

Same thing

assert.throws(() => {
res.setHeader('header2', 2);
}, Error, 'setHeader after write should throw');
res.end()
Copy link
Member

Choose a reason for hiding this comment

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

I think it can be useful checking the error message too. 'Can\'t set headers after they are sent.'

Copy link
Contributor Author

@niklasi niklasi Sep 21, 2016

Choose a reason for hiding this comment

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

I went back and forth with this one. I can see why it could be useful to check the error message, but I can also see why it could be problematic. The way I see it is that the error message is an "implementation detail" and not part of the api and therefore you make the test more fragile if you test the error message. I don't think the test should fail if you change the error message, but on the other hand how do you know if it is the "right" Error? I'm not sure what the best way to do this is, in this context, and I'm more than happy to discuss this.
Btw, this is my first PR for the node-project and I really appreciate your feedback.

Copy link
Member

Choose a reason for hiding this comment

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

If I'm not wrong changing the error message is considered a breaking change so I'm +1 for also checking the error message.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Well, if that's considered a breaking change then I'm also for checking the error message :-)
Thank you for the clarification. I will fix it.

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 have fixed the error message check now.

assert.throws(() => {
res.removeHeader('header2', 2);
}, Error, 'removeHeader after write should throw');
res.end()
Copy link
Member

Choose a reason for hiding this comment

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

Check error message here too.

@santigimeno
Copy link
Member

You're missing some semicolons. Running make jslint will help you identifying formatting issues.

Copy link
Member

@santigimeno santigimeno left a comment

Choose a reason for hiding this comment

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

LGTM with the lint issues fixes and a green CI.

@niklasi
Copy link
Contributor Author

niklasi commented Sep 21, 2016

I have fixed the semicolons now. Thanks for the tip with make jslint.

@santigimeno
Copy link
Member

@santigimeno
Copy link
Member

New CI: https://ci.nodejs.org/job/node-test-pull-request/4193/ the last one disappeared :o

Copy link
Member

@jasnell jasnell left a comment

Choose a reason for hiding this comment

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

LGTM. The tests could be condensed into one but this is perfectly fine also.

res.write('abc');
assert.throws(() => {
res.setHeader('header2', 2);
}, /Can't set headers after they are sent./);
Copy link
Member

Choose a reason for hiding this comment

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

Nit: the final dot should be escaped or removed.

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 have fixed that now.

Copy link
Member

@lpinca lpinca left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@imyller imyller left a comment

Choose a reason for hiding this comment

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

LGTM

@imyller imyller self-assigned this Sep 23, 2016
@imyller
Copy link
Member

imyller commented Sep 23, 2016

I'll start landing this:

  • Four LGTMs
  • No objections
  • Requested changes have been made
  • CI test passed (only unrelated CI failures)

@imyller
Copy link
Member

imyller commented Sep 23, 2016

landed in a5994f7

Thank you for your contribution, @niklasi

@imyller imyller closed this Sep 23, 2016
imyller pushed a commit that referenced this pull request Sep 23, 2016
This change adds tests to make sure an Error is thrown if a header
is added or removed after they are sent.

PR-URL: #8682
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Ilkka Myller <ilkka.myller@nodefield.com>
@imyller imyller removed their assignment Sep 23, 2016
jasnell pushed a commit that referenced this pull request Sep 29, 2016
This change adds tests to make sure an Error is thrown if a header
is added or removed after they are sent.

PR-URL: #8682
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Ilkka Myller <ilkka.myller@nodefield.com>
MylesBorins pushed a commit that referenced this pull request Oct 6, 2016
This change adds tests to make sure an Error is thrown if a header
is added or removed after they are sent.

PR-URL: #8682
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Ilkka Myller <ilkka.myller@nodefield.com>
MylesBorins pushed a commit that referenced this pull request Oct 10, 2016
This change adds tests to make sure an Error is thrown if a header
is added or removed after they are sent.

PR-URL: #8682
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Ilkka Myller <ilkka.myller@nodefield.com>
Fishrock123 pushed a commit that referenced this pull request Oct 11, 2016
This change adds tests to make sure an Error is thrown if a header
is added or removed after they are sent.

PR-URL: #8682
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Ilkka Myller <ilkka.myller@nodefield.com>
rvagg pushed a commit that referenced this pull request Oct 18, 2016
This change adds tests to make sure an Error is thrown if a header
is added or removed after they are sent.

PR-URL: #8682
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Ilkka Myller <ilkka.myller@nodefield.com>
MylesBorins pushed a commit that referenced this pull request Oct 26, 2016
This change adds tests to make sure an Error is thrown if a header
is added or removed after they are sent.

PR-URL: #8682
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Ilkka Myller <ilkka.myller@nodefield.com>
@MylesBorins MylesBorins mentioned this pull request Oct 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
http Issues or PRs related to the http subsystem. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants