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: refactor test-http-expect-continue #19625

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 20 additions & 27 deletions test/parallel/test-http-expect-continue.js
Original file line number Diff line number Diff line change
Expand Up @@ -20,70 +20,63 @@
// USE OR OTHER DEALINGS IN THE SOFTWARE.

'use strict';
require('../common');
const common = require('../common');
const assert = require('assert');
const http = require('http');

let outstanding_reqs = 0;
const test_req_body = 'some stuff...\n';
const test_res_body = 'other stuff!\n';
let sent_continue = false;
let got_continue = false;

function handler(req, res) {
assert.strictEqual(sent_continue, true,
'Full response sent before 100 Continue');
const handler = common.mustCall((req, res) => {
assert.ok(sent_continue, 'Full response sent before 100 Continue');
console.error('Server sending full response...');
res.writeHead(200, {
'Content-Type': 'text/plain',
'ABCD': '1'
});
res.end(test_res_body);
}
});

const server = http.createServer(handler);
server.on('checkContinue', function(req, res) {
const server = http.createServer();
Copy link
Member

Choose a reason for hiding this comment

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

handler is no longer registered as a 'request' listener?

Copy link
Member

Choose a reason for hiding this comment

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

Actually, given the description in the API docs for checkContinue it probably makes more sense to register a common.mustNotCall request listener.

server.on('checkContinue', common.mustCall((req, res) => {
console.error('Server got Expect: 100-continue...');
res.writeContinue();
sent_continue = true;
setTimeout(function() {
handler(req, res);
}, 100);
});
}));
server.listen(0);


server.on('listening', function() {
server.on('listening', common.mustCall(() => {
const req = http.request({
port: this.address().port,
port: server.address().port,
method: 'POST',
path: '/world',
headers: { 'Expect': '100-continue' }
});
console.error('Client sending request...');
outstanding_reqs++;
let body = '';
req.on('continue', function() {
req.on('continue', common.mustCall(() => {
console.error('Client got 100 Continue...');
got_continue = true;
req.end(test_req_body);
});
req.on('response', function(res) {
assert.strictEqual(got_continue, true,
'Full response received before 100 Continue');
}));
req.on('response', common.mustCall((res) => {
assert.ok(got_continue, 'Full response received before 100 Continue');
assert.strictEqual(200, res.statusCode,
`Final status code was ${res.statusCode}, not 200.`);
res.setEncoding('utf8');
res.on('data', function(chunk) { body += chunk; });
res.on('end', function() {
res.on('end', common.mustCall(() => {
console.error('Got full response.');
assert.strictEqual(body, test_res_body, 'Response body doesn\'t match.');
assert.strictEqual(body, test_res_body);
Copy link
Member

Choose a reason for hiding this comment

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

@Trott - is it that the removed error message is too awkward to be of any use, or is there a consensus / guideline to remove error messages from assertion statements?

Copy link
Member Author

@Trott Trott Mar 27, 2018

Choose a reason for hiding this comment

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

By including that assertion message, we suppress the printing of the contents of body and test_res_body when there is in AssertionError. Those values would seem to be useful for debugging. In contrast, the supplied message doesn't provide any useful information IMO.

An alternative would be to replace it with a template literal: `Response body doesn't match. Expected ${test_res_body} but received ${body}.` I prefer simply removing it, but I could go with that if it's deemed important to keep.

Copy link
Member

Choose a reason for hiding this comment

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

thanks for the clarification!

assert.ok('abcd' in res.headers, 'Response headers missing.');
outstanding_reqs--;
if (outstanding_reqs === 0) {
server.close();
process.exit();
}
});
});
});
server.close();
process.exit();
}));
}));
}));