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

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

57 lines
1.3 KiB
JSON
Raw Permalink Normal View History

Enables some unit tests on travis.
2017-01-10 06:43:45 +09: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-10 02:28:48 +09:00
"spec_dir": "build/lib-legacy/test/unit",
Utilize `PDFNodeStream` to run more API unit-tests on Node.js/Travis
2018-01-28 22:34:45 +09:00
"helpers": ["clitests_helper.js"],
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",
Add an annotation storage in order to save annotation data in acroforms
2020-07-22 20:55:52 +09: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-09 00:09:54 +09:00
"api_spec.js",
Add better validation for the "PREFERENCE" kind `AppOptions` Given that the "PREFERENCE" kind is used e.g. to generate the preference-list for the Firefox PDF Viewer, those options need to be carefully validated. With this patch we'll now check this unconditionally in development mode, during testing, and when creating the preferences in the gulpfile.
2024-02-19 20:39:11 +09:00
"app_options_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",
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 20:26:19 +09:00
"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-24 00:14:31 +09:00
"core_utils_spec.js",
Enables some unit tests on travis.
2017-01-10 06:43:45 +09:00
"crypto_spec.js",
Run the `custom_spec` unit-tests in Node.js/Travis (PR 10537 follow-up)
2019-02-27 04:07:06 +09: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-22 04:15:31 +09:00
"default_appearance_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 23:41:02 +09: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-09 00:51:30 +09:00
"document_spec.js",
[editor] Use the `fit-curve` package (issue 15004) Rather than including all of this external code in the PDF.js repository, we should be using the npm package instead. Unfortunately this is slightly more complicated than you'd hope, since the `fit-curve` package (which is older) isn't directly compatible with modern JavaScript modules. In particular, the following cases needed to be considered: - For the development viewer (i.e. `gulp server`) and the unit-tests, we thus need to build a fitCurve-bundle that can be directly `import`ed. - For the actual PDF.js build-targets, we can slightly reduce the sizes by depending on the "raw" `fit-curve` source-code. - For the Node.js unit-tests, the `fit-curve` package can be used as-is.
2022-07-07 06:02:53 +09:00
"editor_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-25 02:03:26 +09:00
"encodings_spec.js",
Enables some unit tests on travis.
2017-01-10 06:43:45 +09:00
"evaluator_spec.js",
Move the `EventBus`, and related functionality, into its own file The size of the `web/ui_utils.js` file has increased over time, as more code has been added to (or moved into) that file. To reduce its size slightly, this patch moves the event-related functionality into a separate file.
2021-12-16 01:09:16 +09:00
"event_utils_spec.js",
Add tests for the font substitution
2023-05-15 00:40:39 +09:00
"font_substitutions_spec.js",
Enables some unit tests on travis.
2017-01-10 06:43:45 +09:00
"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 19:37:54 +09:00
"message_handler_spec.js",
Enable metadata unit tests for Travis CI and Node.js
2017-09-16 05:39:54 +09:00
"metadata_spec.js",
Enables some unit tests on travis.
2017-01-10 06:43:45 +09:00
"murmurhash3_spec.js",
Implement unit tests for the network utility code This should provide 100% coverage for the file.
2017-12-24 00:32:02 +09:00
"network_utils_spec.js",
Adds tests for node_stream
2017-08-05 04:30:37 +09:00
"node_stream_spec.js",
Enables some unit tests on travis.
2017-01-10 06:43:45 +09:00
"parser_spec.js",
Add unit-tests to check that more PDF.js APIs expose the expected functionality Similar to e.g. PR 16587, let's ensure that the `pdf.worker.js` and `pdf.image_decoders.js` files expose the expected functionality.
2023-07-07 19:36:21 +09:00
"pdf.image_decoders_spec.js",
"pdf.worker_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-22 05:40:15 +09:00
"pdf_find_controller_spec.js",
"pdf_find_utils_spec.js",
"pdf_history_spec.js",
Add a unit-test to check that the *official* PDF.js API exposes the expected functionality Until now we've not actually had *any* tests that ensure that the *official* PDF.js API exposes the intended functionality, which means that things can easily break accidentally.
2023-06-22 22:16:25 +09:00
"pdf_spec.js",
Run the PDF.js-viewer API unit-test in Node.js environments (PR 16592 follow-up) It occurred to me that we can actually run this unit-test in Node.js environments by making use of the preprocessor to stub out the browser globals there.
2023-06-26 16:30:13 +09:00
"pdf_viewer.component_spec.js",
Remove the abstract `BaseViewer`-class After the changes in PR 14112 the `PDFViewer`-class is now "identical" to the `BaseViewer`-class and the `PDFSinglePageViewer`-class is just a very thin wrapper around the `BaseViewer`-class. Hence we can rename these files, and also remove the abstract `BaseViewer`-class, which helps reduce some unnecessary "closures" in the *built* viewer. *Please note:* These changes are made in two separate commits, to allow GitHub to preserve `blame` for the affected files.
2022-09-08 18:53:56 +09:00
"pdf_viewer_spec.js",
Enables some unit tests on travis.
2017-01-10 06:43:45 +09:00
"primitives_spec.js",
"stream_spec.js",
Add support for basic structure tree for accessibility. When a PDF is "marked" we now generate a separate DOM that represents the structure tree from the PDF. This DOM is inserted into the <canvas> element and allows screen readers to walk the tree and have more information about headings, images, links, etc. To link the structure tree DOM (which is empty) to the text layer aria-owns is used. This required modifying the text layer creation so that marked items are now tracked.
2021-04-01 07:07:02 +09:00
"struct_tree_spec.js",
Expose `TextLayerRenderTask` in the TypeScript definitions (issue 15016, PR 14013 follow-up) While `TextLayerRenderTask` apparently makes sense in TypeScript environments, given that it's being returned by the `renderTextLayer`-function in the API, we really don't want to extend the *public* API by simply exporting the class directly in `src/pdf.js` since it should never be called/initialized manually. Hence we follow the same pattern as in PR 14013, and add some very basic unit-tests to ensure that `renderTextLayer` always returns a `TextLayerRenderTask`-instance as expected.
2022-06-10 16:53:52 +09:00
"text_layer_spec.js",
Enables some unit tests on travis.
2017-01-10 06:43:45 +09:00
"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",
Add support for saving forms
2020-08-04 02:44:04 +09: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 07:13:52 +09: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-18 04:28:06 +09: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 21:44:03 +09:00
"xfa_parser_spec.js",
XFA - Save filled data in the pdf when downloading the file (Bug 1716288) - when binding (after parsing) we get a map between some template nodes and some data nodes; - so set user data in input handlers in using data node uids in the annotation storage; - to save the form, just put the value we have in the storage in the correct data nodes, serialize the xml as a string and then write the string at the end of the pdf using src/core/writer.js; - fix few bugs around data bindings: - the "Off" issue in Bug 1716980.
2021-06-25 21:31:55 +09:00
"xfa_serialize_data_spec.js",
XFA -- Display text content - display xhtml; - allow spaces in xhtml (xfa-spacerun:yes); - support column layout; - fix some border issues.
2021-03-26 00:54:36 +09:00
"xfa_tohtml_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 07:13:52 +09:00
"xml_spec.js"
Enables some unit tests on travis.
2017-01-10 06:43:45 +09:00
]
}
Reference in New Issue Copy Permalink