pdf.js/test/unit/clitests.json

{
  "spec_dir": "build/lib/test/unit",
  "spec_files": [
    "annotation_spec.js",
    "bidi_spec.js",
    "cff_parser_spec.js",
    "cmap_spec.js",
    "crypto_spec.js",
    "document_spec.js",
    "dom_utils_spec.js",
    "evaluator_spec.js",
    "fonts_spec.js",
    "function_spec.js",
    "murmurhash3_spec.js",
    "parser_spec.js",
    "primitives_spec.js",
    "stream_spec.js",
    "type1_parser_spec.js",
    "ui_utils_spec.js",
    "unicode_spec.js",
    "util_spec.js"
  ]
}
Enables some unit tests on travis. 2017-01-10 06:43:45 +09:00			`{`
Creates 'lib' for the 'dist' build target. 2017-03-02 02:11:39 +09:00			`"spec_dir": "build/lib/test/unit",`
Enables some unit tests on travis. 2017-01-10 06:43:45 +09:00			`"spec_files": [`
Simplify the `FileAttachmentAnnotation` unit-test to avoid having to use the entire API in the test Every other unit-test in `annotation_spec.js` is already only testing the annotation code. Hence it seems unnecessarily convoluted to make use of the API here, when we can (fairly) simply provide the necessary data explicitly as in all the other annotation unit-test. 2017-01-12 22:11:22 +09:00			`"annotation_spec.js",`
Fix inverted calculation of RTL text percentage in bidi. 2017-01-12 01:04:54 +09:00			`"bidi_spec.js",`
Enables some unit tests on travis. 2017-01-10 06:43:45 +09:00			`"cff_parser_spec.js",`
Enable running the `cmap` unit-tests on Travis by utilizing a `NodeCMapReaderFactory` 2017-02-17 21:44:49 +09:00			`"cmap_spec.js",`
Enables some unit tests on travis. 2017-01-10 06:43:45 +09:00			`"crypto_spec.js",`
Replace direct lookup of `uniquePrefix`/`idCounters`, in `Page` instances, with an `idFactory` containing an `createObjId` method instead We're currently making use of `uniquePrefix`/`idCounters` in multiple files, to create unique object id's, and adding a new occurrence of them requires some care to ensure that an object id isn't accidentally reused. Furthermore, having to pass around multiple parameters as we currently do seem like something you want to avoid. Instead, this patch adds a factory which means that there's only one thing that needs to be passed around. And since it's now only necessary to call a method in order to obtain a unique object id, the details are thus abstracted away at the call-sites which avoids accidental reuse of object id's. To test that this works as expected a very simple `Page` unit-test is added, and the existing `Annotation layer` tests are also adjusted slightly. 2017-01-09 00:51:30 +09:00			`"document_spec.js",`
Enables some unit tests on travis. 2017-01-10 06:43:45 +09:00			`"dom_utils_spec.js",`
			`"evaluator_spec.js",`
			`"fonts_spec.js",`
			`"function_spec.js",`
			`"murmurhash3_spec.js",`
			`"parser_spec.js",`
			`"primitives_spec.js",`
			`"stream_spec.js",`
			`"type1_parser_spec.js",`
Enable running the `ui_utils` unit-tests on Travis With the exception of just one test-case, all the current `ui_utils` unit-tests can run successfully on Node.js (since most of them doesn't rely on the DOM). To get this working, I had to first of all add a new `LIB` build flag such that `gulp lib` produces a `web/pdfjs.js` file that is able to load `pdf.js` successfully. Second of all, since neither `document` nor `navigator` is available in Node.js, `web/ui_utils.js` was adjusted slightly to avoid errors. 2017-04-25 05:07:00 +09:00			`"ui_utils_spec.js",`
Enables some unit tests on travis. 2017-01-10 06:43:45 +09:00			`"unicode_spec.js",`
			`"util_spec.js"`
			`]`
			`}`