pdf.js/test/unit/fonts_spec.js

/* globals describe, it, expect, checkProblematicCharRanges */

'use strict';

describe('Fonts', function() {
  it('checkProblematicCharRanges', function() {
    var EXPECTED_PERCENTAGE = 45;
    var result = checkProblematicCharRanges();

    expect(result.percentage).toBeLessThan(EXPECTED_PERCENTAGE);
  });
});
Remove unused globals from fonts unit test file 2016-08-27 23:20:03 +02:00			`/* globals describe, it, expect, checkProblematicCharRanges */`
Add a unit-test to check that `ProblematicCharRanges` contains valid entries When adding new entries to `ProblematicCharRanges`, you have to be careful to not make any mistakes since that could cause glyph mapping issues. Currently the existing reference tests should probably help catch any errors, but based on experience I think that having a unit-test which specifically checks `ProblematicCharRanges` would be both helpful and timesaving when modifying/reviewing changes to this code. Hence this patch which adds a function (and unit-test) that is used to validate the entries in `ProblematicCharRanges`, and also checks that we don't accidentally add more character ranges than the Private Use Area can actually contain. The way that the validation code, and thus the unit-test, is implemented also means that we have an easy way to tell how much of the Private Use Area is potentially utilized by re-mapped characters. 2016-08-13 12:20:03 +02:00
			`'use strict';`

			`describe('Fonts', function() {`
			`it('checkProblematicCharRanges', function() {`
			`var EXPECTED_PERCENTAGE = 45;`
			`var result = checkProblematicCharRanges();`

			`expect(result.percentage).toBeLessThan(EXPECTED_PERCENTAGE);`
			`});`
			`});`