pdf.js/test/unit/unit_test.html

<!DOCTYPE html>
<html>
<head>
  <title>pdf.js unit test</title>

  <link rel="stylesheet" type="text/css" href="../../node_modules/jasmine-core/lib/jasmine-core/jasmine.css">

  <script src="../../node_modules/requirejs/require.js"></script>
  <script src="../../node_modules/jasmine-core/lib/jasmine-core/jasmine.js"></script>
  <script src="../../node_modules/jasmine-core/lib/jasmine-core/jasmine-html.js"></script>
  <script src="testreporter.js"></script>
  <script src="jasmine-boot.js"></script>

  <!-- include spec files here... -->
  <script src="primitives_spec.js"></script>
  <script src="cff_parser_spec.js"></script>
  <script src="type1_parser_spec.js"></script>
  <script src="fonts_spec.js"></script>
  <script src="unicode_spec.js"></script>
  <script src="function_spec.js"></script>
  <script src="crypto_spec.js"></script>
  <script src="evaluator_spec.js"></script>
  <script src="stream_spec.js"></script>
  <script src="parser_spec.js"></script>
  <script src="api_spec.js"></script>
  <script src="metadata_spec.js"></script>
  <script src="ui_utils_spec.js"></script>
  <script src="util_spec.js"></script>
  <script src="cmap_spec.js"></script>
  <script src="annotation_layer_spec.js"></script>
  <script src="network_spec.js"></script>
  <script src="dom_utils_spec.js"></script>
</head>
<body>
</body>
</html>
Use test.py for unit tests too. 2012-04-19 12:32:24 -07:00			`<!DOCTYPE html>`
			`<html>`
			`<head>`
			`<title>pdf.js unit test</title>`

Updates Jasmine version. 2016-03-29 09:34:13 -05:00			`<link rel="stylesheet" type="text/css" href="../../node_modules/jasmine-core/lib/jasmine-core/jasmine.css">`
Use test.py for unit tests too. 2012-04-19 12:32:24 -07:00
Use RequireJS in the viewer, examples and tests. 2015-12-16 15:03:06 -06:00			`<script src="../../node_modules/requirejs/require.js"></script>`
Updates Jasmine version. 2016-03-29 09:34:13 -05:00			`<script src="../../node_modules/jasmine-core/lib/jasmine-core/jasmine.js"></script>`
			`<script src="../../node_modules/jasmine-core/lib/jasmine-core/jasmine-html.js"></script>`
Remove type="text/javascript" from script tags. "text/javascript" is not a correct MIME type (the correct one is "application/javascript") but it's not even needed; all browsers default to the correct type and treat it as executable JS when type is ommited. Since not all browsers recognize the "application/javascript" MIME type the only way to both stay compliant and to support all popular browsers is to omit the type. It's also shorter this way. 2014-05-13 02:41:01 +02:00			`<script src="testreporter.js"></script>`
Updates Jasmine version. 2016-03-29 09:34:13 -05:00			`<script src="jasmine-boot.js"></script>`
Use test.py for unit tests too. 2012-04-19 12:32:24 -07:00
			`<!-- include spec files here... -->`
Adds UMD headers to core, display and shared files. 2015-11-21 10:32:47 -06:00			`<script src="primitives_spec.js"></script>`
Split the font_spec.js unit-tests into cff_parser_spec.js and type1_parser_spec.js Re: issue 7261. Given the we have `gulp fonttest`, which tests the `fonts.js` functionality at a higher level, and that we have a lot of font specific reference tests, I'm not convinced that we also need unit-tests for it. 2016-05-03 09:22:22 +02:00			`<script src="cff_parser_spec.js"></script>`
			`<script src="type1_parser_spec.js"></script>`
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			`<script src="fonts_spec.js"></script>`
Add basic unit-tests for unicode.js Re: issue 7261. 2016-05-19 13:54:28 +02:00			`<script src="unicode_spec.js"></script>`
Remove type="text/javascript" from script tags. "text/javascript" is not a correct MIME type (the correct one is "application/javascript") but it's not even needed; all browsers default to the correct type and treat it as executable JS when type is ommited. Since not all browsers recognize the "application/javascript" MIME type the only way to both stay compliant and to support all popular browsers is to omit the type. It's also shorter this way. 2014-05-13 02:41:01 +02:00			`<script src="function_spec.js"></script>`
			`<script src="crypto_spec.js"></script>`
			`<script src="evaluator_spec.js"></script>`
			`<script src="stream_spec.js"></script>`
			`<script src="parser_spec.js"></script>`
			`<script src="api_spec.js"></script>`
			`<script src="metadata_spec.js"></script>`
Use binary search in getVisibleElements() 2014-12-26 17:43:13 +01:00			`<script src="ui_utils_spec.js"></script>`
Remove type="text/javascript" from script tags. "text/javascript" is not a correct MIME type (the correct one is "application/javascript") but it's not even needed; all browsers default to the correct type and treat it as executable JS when type is ommited. Since not all browsers recognize the "application/javascript" MIME type the only way to both stay compliant and to support all popular browsers is to omit the type. It's also shorter this way. 2014-05-13 02:41:01 +02:00			`<script src="util_spec.js"></script>`
			`<script src="cmap_spec.js"></script>`
Add tests and documentation for the annotation border style class This patch adds: - Unit tests for the annotation border style class - Regression test (self-made) for the annotation border style class - Documentation generation using JSDoc 2014-12-25 21:04:01 +01:00			`<script src="annotation_layer_spec.js"></script>`
Makes PDF data reading Streams API friendly. 2016-02-09 14:55:11 -06:00			`<script src="network_spec.js"></script>`
Removes global PDFJS usage from the src/core/. 2016-03-02 18:48:21 -06:00			`<script src="dom_utils_spec.js"></script>`
Use test.py for unit tests too. 2012-04-19 12:32:24 -07:00			`</head>`
			`<body>`
			`</body>`
			`</html>`