Try to re-factor the integration-boot.js file (and related code)

[Snuffleupagus]

For consistency/maintainability reasons, it would probably be helpful if the new integration-boot.js (and related code) would look more like the existing code used with the unit/font-tests. To that end, I'd suggest the following (not an exhaustive list):

• Move, and re-name, the new file to test/integration/jasmine-boot.js and possibly adding a new test/integration/integration_test.html file as well as part of these changes.
• Re-factor the integration-boot.js, and any related code in test/test.js, file to follow the same general pattern as used with e.g. https://github.com/mozilla/pdf.js/blob/master/test/unit/jasmine-boot.js and https://github.com/mozilla/pdf.js/blob/master/test/unit/unit_test.html respectively https://github.com/mozilla/pdf.js/blob/master/test/font/jasmine-boot.js and https://github.com/mozilla/pdf.js/blob/master/test/font/font_test.html
• Try to use the same result-reporting mechanism as used with e.g. the unit/font-tests.
• Actually include the browser name in the output, since that's often helpful; note that the current output doesn't include this information:

  pdf.js/test/integration-boot.js

  Lines 35 to 40 in 00b4f86

  	if (result.failedExpectations.length > 0) {
  	++results.failures;
  	console.log(`TEST-UNEXPECTED-FAIL | ${result.description}`);
  	} else {
  	console.log(`TEST-PASSED | ${result.description}`);
  	}

  whereas the unit/font-tests does:

  pdf.js/test/test.js

  Lines 797 to 798 in 00b4f86

  	var message =
  	data.status + " | " + data.description + " | in " + session.name;

[aashrafh]

Can I work on it?

[timvandermeij]

Sure, feel free to work on this.

[simran212530]

Hey,

Can I work on this?

[Snuffleupagus]

This issue is unlikely to be a good beginner bug, if you're not already at least somewhat familiar with the PDF.js code-base and its test-suites.