From b1f0c353f252279c18c3d31a6d4cb932c5999287 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?V=C3=ADtor=20De=20Ara=C3=BAjo?= Date: Fri, 3 Oct 2025 11:23:14 +0000 Subject: [PATCH 1/2] Add Test Impact Analysis troubleshooting note for Python --- content/en/tests/test_impact_analysis/troubleshooting/_index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/tests/test_impact_analysis/troubleshooting/_index.md b/content/en/tests/test_impact_analysis/troubleshooting/_index.md index 8da10c5fcd9e2..b5c9e4bcde9e6 100644 --- a/content/en/tests/test_impact_analysis/troubleshooting/_index.md +++ b/content/en/tests/test_impact_analysis/troubleshooting/_index.md @@ -48,6 +48,8 @@ Test Impact Analysis performs test impact analysis based on code coverage to det If you are authoring a commit that includes any of those cases, you can force-disable test skipping in Test Impact Analysis by adding `ITR:NoSkip` (case insensitive) anywhere in your Git commit message. +In Python, some packages, such as `sumy` and `sendgrid`, install modules under the `test.*` or `tests.*` package namespace, which can cause tests to be detected as third-party packages if they are located in a folder with the same name. If you use one of those packages, coverage data for tests may be incomplete, which may cause a test to be skipped when it should have been run. In this case, you should disable Test Impact Analysis for your project. This is a known issue that will be resolved in a future version of `dd-trace-py`. + ## Further reading {{< partial name="whats-next/whats-next.html" >}} From d78b72078d20a1bd89bc9033a59df6c0dd5e97be Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?V=C3=ADtor=20De=20Ara=C3=BAjo?= Date: Mon, 6 Oct 2025 16:42:07 +0000 Subject: [PATCH 2/2] add workaround information --- .../en/tests/test_impact_analysis/troubleshooting/_index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/en/tests/test_impact_analysis/troubleshooting/_index.md b/content/en/tests/test_impact_analysis/troubleshooting/_index.md index b5c9e4bcde9e6..1545e303e9f5c 100644 --- a/content/en/tests/test_impact_analysis/troubleshooting/_index.md +++ b/content/en/tests/test_impact_analysis/troubleshooting/_index.md @@ -48,7 +48,9 @@ Test Impact Analysis performs test impact analysis based on code coverage to det If you are authoring a commit that includes any of those cases, you can force-disable test skipping in Test Impact Analysis by adding `ITR:NoSkip` (case insensitive) anywhere in your Git commit message. -In Python, some packages, such as `sumy` and `sendgrid`, install modules under the `test.*` or `tests.*` package namespace, which can cause tests to be detected as third-party packages if they are located in a folder with the same name. If you use one of those packages, coverage data for tests may be incomplete, which may cause a test to be skipped when it should have been run. In this case, you should disable Test Impact Analysis for your project. This is a known issue that will be resolved in a future version of `dd-trace-py`. +### Packages incorrectly detected as third-party + +In Python, some packages, such as `sumy` and `sendgrid`, install modules under the `test.*` or `tests.*` package namespace. This can cause tests to be detected as third-party packages if they are located in a folder with the same name. If you use one of those packages, coverage data for tests may be incomplete, which may cause a test to be skipped when it should have been run. To avoid this issue, you can set the `DD_THIRD_PARTY_DETECTION_EXCLUDES` environment variable to a list of such third-party packages (for example, `DD_THIRD_PARTY_DETECTION_EXCLUDES=sumy,sendgrid`). This is a known issue that is scheduled to be resolved in a future version of `dd-trace-py`. ## Further reading