From bdde1336f1431e953113e479b9fb2f2017ef135d Mon Sep 17 00:00:00 2001 From: Jonas Jenwald Date: Thu, 22 Jul 2021 00:26:21 +0200 Subject: [PATCH] Include the `font`/`integration`/`unit`-test folders in the LGTM report By default all files/folders classified as test-code are excluded in the LGTM report, however I do believe that it makes sense to include at least the `font`/`integration`/`unit`-test folders. It seems pretty obvious that you want to avoid *accidentally* introducing any simple logical errors in the tests (and not only in the main code), to ensure that e.g. the unit-tests actually test the desired thing. Hopefully I've interpreted the information at https://lgtm.com/help/lgtm/customizing-file-classification correctly, however note that we may need to land this patch to actually see any difference in the results. --- lgtm.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/lgtm.yml b/lgtm.yml index 3b3b99fa8a8f6..24f1ebe1f3363 100644 --- a/lgtm.yml +++ b/lgtm.yml @@ -1,3 +1,9 @@ +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