Sakurai/pdf.js
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
pdf.js/test/unit/clitests.json

47 lines
1.0 KiB
JSON
Raw Normal View History

Enables some unit tests on travis.
2017-01-09 15:43:45 -06:00
{
[api-minor] Rename `-es5` to `-legacy`, to reduce confusion over what's actually supported (issue 12976) *Please note that this will also require some edits of the Wiki.*
2021-02-09 18:28:48 +01:00
"spec_dir": "build/lib-legacy/test/unit",
Utilize `PDFNodeStream` to run more API unit-tests on Node.js/Travis
2018-01-28 14:34:45 +01:00
"helpers": [
"clitests_helper.js"
],
Enables some unit tests on travis.
2017-01-09 15:43:45 -06: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 14:11:22 +01:00
"annotation_spec.js",
Add an annotation storage in order to save annotation data in acroforms
2020-07-22 13:55:52 +02:00
"annotation_storage_spec.js",
Enable running a subset of the API unit-tests on Travis Notably, this patch skips all canvas rendering tests in Node.js.
2017-04-08 17:09:54 +02:00
"api_spec.js",
Fix inverted calculation of RTL text percentage in bidi.
2017-01-12 00:04:54 +08:00
"bidi_spec.js",
Enables some unit tests on travis.
2017-01-09 15:43:45 -06:00
"cff_parser_spec.js",
Enable running the `cmap` unit-tests on Travis by utilizing a `NodeCMapReaderFactory`
2017-02-17 13:44:49 +01:00
"cmap_spec.js",
Add unit-tests for colorspace.js Added unit-tests for DeviceGray, DeviceRGB and DeviceCMYK Added unit-tests for CalGray Added unit-tests for CalRGB Removed redundant code Added unit-tests for LabCS Added unit-tests for IndexedCS Update comment Change lookup to Uint8Array as mentioned in pdf specs(these tests will pass after PR #8666 is merged). Added unit-tests for AlternateCS Resolved code-style issues Fixed code-style issues Addressed issues pointed out in https://github.com/mozilla/pdf.js/pull/8611#pullrequestreview-52865469
2017-07-05 16:56:19 +05:30
"colorspace_spec.js",
Move worker-thread only functions from `src/shared/util.js` and into a new `src/core/core_utils.js` file The `src/shared/util.js` file is being bundled into both the `pdf.js` and `pdf.worker.js` files, meaning that its code is by definition duplicated. Some main-thread only utility functions have already been moved to a separate `src/display/display_utils.js` file, and this patch simply extends that concept to utility functions which are used *only* on the worker-thread. Note in particular the `getInheritableProperty` function, which expects a `Dict` as input and thus *cannot* possibly ever be used on the main-thread.
2019-02-23 16:14:31 +01:00
"core_utils_spec.js",
Enables some unit tests on travis.
2017-01-09 15:43:45 -06:00
"crypto_spec.js",
Run the `custom_spec` unit-tests in Node.js/Travis (PR 10537 follow-up)
2019-02-26 20:07:06 +01:00
"custom_spec.js",
Add a parser to get font data from the default appearance (#12831) * Add a parser to get font data from the default appearance - pdfium & poppler use a special parser too to get these info. * Update src/core/default_appearance.js Co-authored-by: Jonas Jenwald <jonas.jenwald@gmail.com> Co-authored-by: Jonas Jenwald <jonas.jenwald@gmail.com>
2021-01-21 11:15:31 -08:00
"default_appearance_spec.js",
Optimize PNG compression in SVG backend on Node.js Use the environment's zlib implementation if available to get reasonably-sized SVG files when an XObject image is converted to PNG. The generated PNG is not optimal because we do not use a PNG predictor. Futher, when our SVG backend is run in a browser, the generated PNG images will still be unnecessarily large (though the use of blob:-URLs when available should reduce the impact on memory usage). If we want to optimize PNG images in browsers too, we can either try to use a DEFLATE library such as pako, or re-use our XObject image painting logic in src/display/canvas.js. This potential improvement is not implemented by this commit Tested with: - Node.js 8.1.3 (uses zlib) - Node.js 0.11.12 (uses zlib) - Node.js 0.10.48 (falls back to inferior existing implementation). - Chrome 59.0.3071.86 - Firefox 54.0 Tests: Unit test on Node.js: ``` $ gulp lib $ JASMINE_CONFIG_PATH=test/unit/clitests.json node ./node_modules/.bin/jasmine --filter=SVG ``` Unit test in browser: Run `gulp server` and open http://localhost:8888/test/unit/unit_test.html?spec=SVGGraphics To verify that the patch works as desired, ``` $ node examples/node/pdf2svg.js test/pdfs/xobject-image.pdf $ du -b svgdump/xobject-image-1.svg # ^ Calculates the file size. Confirm that the size is small # (784 instead of 80664 bytes). ```
2017-07-06 15:08:37 +02:00
"display_svg_spec.js",
Rename the `src/display/dom_utils.js` file to `src/display/display_utils.js` This file (currently) contains not only DOM-specific helper functions/classes, but is used generally for various helper code relevant for main-thread functionality.
2019-02-23 15:41:02 +01:00
"display_utils_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-08 16:51:30 +01:00
"document_spec.js",
Implement unit tests for the encodings and fix missing items Initially I just implemented the unit tests, but quickly found that they were failing my expectation of having a size of 256 items. Some of them did contain 256 items and some did not. I looked up various resources and figured that they indeed all need to have 256 items. One of the good resources is https://github.com/davidben/poppler/blob/master/poppler/FontEncodingTables.cc Aside from some missing `notdef` (empty string) entries at the end of the arrays, which I assume causes issues since it may cause out-of-bounds array access which in JavaScript gives `undefined`, there was a `notdef` entry missing in the `MacExpertEncoding`, causing the entries after that to be shifted. This fix for this is similar to the one in #8589. The unit tests verify that, for known encoding names, the return value is not only an array, but that it is also of the right length and contains only strings.
2017-12-24 18:03:26 +01:00
"encodings_spec.js",
Enables some unit tests on travis.
2017-01-09 15:43:45 -06:00
"evaluator_spec.js",
"function_spec.js",
Move `MessageHandler` into a separate `src/shared/message_handler.js` file The `MessageHandler` itself, and its assorted helper functions, are currently the single largest[1] piece of code in the `src/shared/util.js` file. By moving this code into its own file, `src/shared/util.js` thus becomes smaller and more manageable.
2018-06-04 12:37:54 +02:00
"message_handler_spec.js",
Enable metadata unit tests for Travis CI and Node.js
2017-09-15 22:39:54 +02:00
"metadata_spec.js",
Enables some unit tests on travis.
2017-01-09 15:43:45 -06:00
"murmurhash3_spec.js",
Implement unit tests for the network utility code This should provide 100% coverage for the file.
2017-12-23 16:32:02 +01:00
"network_utils_spec.js",
Adds tests for node_stream
2017-08-05 01:00:37 +05:30
"node_stream_spec.js",
Enables some unit tests on travis.
2017-01-09 15:43:45 -06:00
"parser_spec.js",
Implement a basic unit test for the find controller This commit shows that we can now unit test the find controller and that executing regular queries works. Note that this is only a first step and not a complete suite of unit tests for all possible options of the find controller. While writing this unit test, I found two smaller issues that I addressed directly. The first one is that in the previous find controller refactoring I forgot to rename some occurrences of a now private member variable. Fortunately this did not cause any bugs since we did have a public getter and the fetched value may be changed by reference, but it's nevertheless good to fix. The second issue is that some entries in the `test/unit/clitests.json` file were not correct, resulting in these tests not being executed on e.g., Travis CI.
2018-09-21 22:40:15 +02:00
"pdf_find_controller_spec.js",
"pdf_find_utils_spec.js",
"pdf_history_spec.js",
Enables some unit tests on travis.
2017-01-09 15:43:45 -06:00
"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-24 22:07:00 +02:00
"ui_utils_spec.js",
Enables some unit tests on travis.
2017-01-09 15:43:45 -06:00
"unicode_spec.js",
Add support for saving forms
2020-08-03 19:44:04 +02:00
"util_spec.js",
Save form data in XFA datasets when pdf is a mix of acroforms and xfa (#12344) * Move display/xml_parser.js in shared to use it in worker * Save form data in XFA datasets when pdf is a mix of acroforms and xfa Co-authored-by: Brendan Dahl <brendan.dahl@gmail.com>
2020-09-09 00:13:52 +02:00
"writer_spec.js",
XFA - Add a lexer/parser for FormCalc language (#12936) - the language specifications are: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.364.2157&rep=rep1&type=pdf#page=1049 - it can be used to: * as a scripting language for calculation, validations, ... * in SOM expressions to select nodes: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.364.2157&rep=rep1&type=pdf#page=101
2021-02-17 11:28:06 -08:00
"xfa_formcalc_spec.js",
XFA - Add a parser for XFA files - the parser is base on a class extending XMLParserBase - it handle xml namespaces: * each namespace is assocated with a builder * builder builds nodes belonging to the namespace * when a node is inserted in the parent namespace compatibility is checked (if required) - to avoid name collision between xml names and object properties, use Symbol.
2021-02-01 13:44:03 +01:00
"xfa_parser_spec.js",
Save form data in XFA datasets when pdf is a mix of acroforms and xfa (#12344) * Move display/xml_parser.js in shared to use it in worker * Save form data in XFA datasets when pdf is a mix of acroforms and xfa Co-authored-by: Brendan Dahl <brendan.dahl@gmail.com>
2020-09-09 00:13:52 +02:00
"xml_spec.js"
Enables some unit tests on travis.
2017-01-09 15:43:45 -06:00
]
}
Reference in New Issue Copy Permalink