pdf.js/test/unit/clitests.json
Tim van der Meij 1b402996cf
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-30 18:32:34 +02:00

39 lines
813 B
JSON

{
"spec_dir": "build/lib/test/unit",
"helpers": [
"clitests_helper.js"
],
"spec_files": [
"annotation_spec.js",
"api_spec.js",
"bidi_spec.js",
"cff_parser_spec.js",
"cmap_spec.js",
"colorspace_spec.js",
"crypto_spec.js",
"display_svg_spec.js",
"document_spec.js",
"dom_utils_spec.js",
"encodings_spec.js",
"evaluator_spec.js",
"function_spec.js",
"message_handler_spec.js",
"metadata_spec.js",
"murmurhash3_spec.js",
"network_utils_spec.js",
"node_stream_spec.js",
"parser_spec.js",
"pdf_find_controller_spec.js",
"pdf_find_utils_spec.js",
"pdf_history_spec.js",
"primitives_spec.js",
"stream_spec.js",
"type1_parser_spec.js",
"ui_utils_spec.js",
"unicode_spec.js",
"util_spec.js"
]
}