- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
This page provides information to help you troubleshot issues with Test Visibility. If you need additional help, contact Datadog Support.
localhost:8126
), or if accessible on another hostname or port, make sure you run your tests with the appropriate Agent hostname set in the DD_AGENT_HOST
and the appropriate port in DD_TRACE_AGENT_PORT
environment variables. You can activate debug mode in the tracer to check if it’s able to connect to the Agent.datadog-ci
but some or all tests are missingIf you are uploading JUnit test report files with datadog-ci
CLI and you do not see the tests, it is likely the tests are being discarded because the report is considered incorrect.
The following aspects make a JUnit test report incorrect:
If you can see test results data in the Test Runs tab, but not the Tests tab, Git metadata (repository, commit, or branch) is probably missing. To confirm this is the case, open a test execution in the Test Runs section, and check that there is no git.repository_url
, git.commit.sha
, or git.branch
. If these tags are not populated, nothing shows in the Tests section.
Tracers first use the environment variables, if any, set by the CI provider to collect Git information. See Running tests inside a container for a list of environment variables that the tracer attempts to read for each supported CI provider. At a minimum, this populates the repository, commit hash, and branch information.
Next, tracers fetch Git metadata using the local .git
folder, if present, by executing git
commands. This populates all Git metadata fields, including commit message, author, and committer information. Ensure the .git
folder is present and the git
binary is installed and in $PATH
. This information is used to populate attributes not detected in the previous step.
You can also provide Git information manually using environment variables, which override information detected by any of the previous steps.
The supported environment variables for providing Git information are:
DD_GIT_REPOSITORY_URL
(required)git@github.com:MyCompany/MyApp.git
, https://github.com/MyCompany/MyApp.git
DD_GIT_COMMIT_SHA
(required)a18ebf361cc831f5535e58ec4fae04ffd98d8152
DD_GIT_BRANCH
develop
DD_GIT_TAG
1.0.1
DD_GIT_COMMIT_MESSAGE
Set release number
DD_GIT_COMMIT_AUTHOR_NAME
John Smith
DD_GIT_COMMIT_AUTHOR_EMAIL
john@example.com
DD_GIT_COMMIT_AUTHOR_DATE
2021-03-12T16:00:28Z
DD_GIT_COMMIT_COMMITTER_NAME
Jane Smith
DD_GIT_COMMIT_COMMITTER_EMAIL
jane@example.com
DD_GIT_COMMIT_COMMITTER_DATE
2021-03-12T16:00:28Z
If no CI provider environment variables are found, tests results are sent with no Git metadata.
If you cannot see the total test time, it is likely that test suite level visibility is not enabled. To confirm, check if your language supports test suite level visibility in Supported features. If test suite level visibility is supported, update your tracer to the latest version.
If you still don’t see the total time after updating the tracer version, contact Datadog support for help.
The total time is defined as the sum of the maximum test session durations.
The test status numbers are calculated based on the unique tests that were collected. The uniqueness of a test is defined not only by its suite and name, but by its test parameters and test configurations as well.
If the numbers are lower than expected, it is likely that either the library or the tool you are using to collect test data cannot collect test parameters and/or some test configurations.
If the same test is collected several times for the same commit but with different status, the aggregated result follows the algorithm in the table below:
Test Status - First Try | Test Status - Retry #1 | Result |
---|---|---|
Passed | Passed | Passed |
Passed | Failed | Passed |
Passed | Skipped | Passed |
Failed | Passed | Passed |
Failed | Failed | Failed |
Failed | Skipped | Failed |
Skipped | Passed | Passed |
Skipped | Failed | Failed |
Skipped | Skipped | Skipped |
The default branch is used to power some features of the products, namely:
Default branches list on the Tests page: This list only displays default branches. Setting the wrong default branch can result in missing or incorrect data in the default branches list.
New flaky tests: Tests that are not currently classified as flaky in the default branch. If the default branch is not properly set, this could lead to a wrong number of detected new flaky tests.
Pipelines list: The pipelines list only displays default branches. Setting the wrong default branch can result in missing or incorrect data in the pipelines list.
If you have admin access, you can update it from the Repository Settings Page.
Other symptoms of the same issue include:
It is likely that the test case configuration is unstable because one or more of the test parameters are non-deterministic (for instance, they include current date or a random number).
The best way to fix this is to make sure that the test parameters are the same between test runs.
Additional helpful documentation, links, and articles: