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_HOSTand the appropriate port in
DD_TRACE_AGENT_PORTenvironment variables. You can activate debug mode in the tracer to check if it’s able to connect to the Agent.
If you can see test results data in the Test Runs tab, but not the Tests tab, Git metadata (repository, commit and/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.branch. If these tags are not populated, nothing shows in the Tests section.
.gitfolder by executing
gitcommands. This is the preferred approach, as it populates all Git metadata fields, including commit message, author and committer information. Ensure the
.gitfolder is present and the
gitbinary is installed and in
.gitfolder is not present, or the
gitbinary is not installed, tracers fallback to use the environment variables set by the CI provider to collect Git information. See the Running tests inside a container page 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.
If you have another issue, or the above solutions don’t work, contact Support for troubleshooting help.