path_classifiers:
  test:
    - exclude: test/font
    - exclude: test/integration
    - exclude: test/unit

queries:
  # Already handled by the "no-unused-vars" ESLint rule.
  - exclude: js/unused-local-variable
  - exclude: js/useless-assignment-to-local

path_classifiers:
  test:
    - exclude: test
    - test/resources

queries:
  # Already handled by the "no-unused-vars" ESLint rule.
  - exclude: js/unused-local-variable
  - exclude: js/useless-assignment-to-local

Include most of the `test`-folder in the LGTM report (PR 13772 follow-up)
Include most of the `test`-folder in the LGTM report (PR 13772 follow-up)

Given that PR 13772 seem to have worked as intended, it probably cannot hurt to enable the LGTM report for *most* of the remaining code in the `test`-folder. (The one remaining exception is code which originated *outside* of the PDF.js project.)

*Please note:* We'll need to land this patch to actually see any difference in the LGTM results.
