Re-factor the PDFDataRangeTransport unit-tests and enable them in Node.js/Travis

[Snuffleupagus]

There doesn't appear to be any particular reason for only running these unit-tests in browsers, since the PDFDataRangeTransport functionality itself should be back-end agnostic.

[Snuffleupagus]

/botio unittest

[pdfjsbot]

From: Bot.io (Linux m4)

---

Received

Command cmd_unittest from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.67.70.0:8877/327d8bff7a44e5e/output.txt

[pdfjsbot]

From: Bot.io (Windows)

---

Received

Command cmd_unittest from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.215.176.217:8877/6f3a1e6e532fc0b/output.txt

[pdfjsbot]

From: Bot.io (Linux m4)

---

Success

Full output at http://54.67.70.0:8877/327d8bff7a44e5e/output.txt

Total script time: 2.84 mins

• Unit Tests: Passed

[pdfjsbot]

From: Bot.io (Windows)

---

Success

Full output at http://54.215.176.217:8877/6f3a1e6e532fc0b/output.txt

Total script time: 5.33 mins

• Unit Tests: Passed

[timvandermeij]

Thank you for doing this!

[Snuffleupagus]

Thanks for the very quick review!

I believe that we're now running all the possible unit-tests in Node.js/Travis, with the sole exception of

pdf.js/test/unit/api_spec.js

Lines 656 to 672 in ff74a66

	it('gets attachments', function(done) {
	if (isNodeJS()) { // The PDF file used is a linked test-case.
	pending('TODO: Use a non-linked test-case.');
	}
	var loadingTask = getDocument(buildGetDocumentParams('bug766138.pdf'));
	var promise = loadingTask.promise.then(function (pdfDoc) {
	return pdfDoc.getAttachments();
	});
	promise.then(function (data) {
	var attachment = data['Press Quality.joboptions'];
	expect(attachment.filename).toEqual('Press Quality.joboptions');
	expect(attachment.content instanceof Uint8Array).toBeTruthy();
	expect(attachment.content.length).toEqual(30098);
	loadingTask.destroy().then(done);
	}).catch(done.fail);
	});