- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Test Optimization integrates with other developer-oriented Datadog products as well as external partners such as GitHub to streamline developer workflows with features including being able to:
These features are available for all Test Optimization customers, and they do not require usage of the Datadog GitHub integration.
Datadog integrates with GitHub to show summaries of test results directly in your pull request comments. Each summary contains an overview of the tests executions, flakiness information, error messages for failed tests, performance regressions, and code coverage changes.
With this information, developers get instant feedback about their tests results, and they can debug any failed or flaky tests without leaving the pull request view.
You can enable test summaries in pull requests with the following steps:
Comments only appear on pull requests that were opened before the test run and that have run at least one test for an enabled test service.
With Test Optimization, you can create and open pre-filled GitHub issues with relevant context into your tests as well as deep links back to Datadog for more streamlined debugging workflows. Creating issues directly from Test Optimization can help you track and maintain accountability for test failures and flaky tests.
You can create pre-filled GitHub issues from three areas within Test Optimization:
The overview page for any commit can be discovered through a particular branch or from within any particular test.
From the Commit Overview page, click on any row in the Failed Tests
or New Flaky Tests
tables and select Open issue in GitHub.
From this page, click on any row in the Flaky Tests table and select Open issue in GitHub.
From within a specific test run, click the Actions button and select Open issue in GitHub.
You also have the option to copy an issue description in Markdown for pasting test details elsewhere. The Markdown description contains information such as the test execution link, service, branch, commit, author, and error.
Below is what a pre-filled GitHub issue might look like:
With Case Management, you can create and open pre-filled Jira issues that contain relevant context related to your tests, as well as deep links back to Datadog for more streamlined debugging workflows. Creating issues directly from Test Optimization can help you track and maintain accountability for test failures and flaky tests.
When you update the status of a Jira issue, the status in Case Management updates and reflects the latest case status.
After you have set up the Jira integration, you can create cases from three areas within Test Optimization:
You can manually create a Jira issue from a case in Case Management by clicking Shift + J
.
The overview page for any commit can be discovered through a particular branch or from within any particular test.
From the Commit Overview page, click on any row in the Failed Tests
or New Flaky Tests
tables and select Create case.
From this page, click on any row in the Flaky Tests table and select Create case.
From within a specific test run, click the Actions button and select Create case.
For more information about configuring the Jira integration, see the Case Management documentation.
After detecting a failed and/or flaky test within Datadog, you have the option to open that test in GitHub or your IDE to fix it immediately.
Under the Error Message section in the Overview tab of a test run, click the View Code button to view the relevant lines of code for that test within Visual Studio Code, IntelliJ, or GitHub.
The order of options in this dropdown changes depending on the language your test was written in:
Optionally, you can set up the GitHub integration to open the source code for a failed or flaky test in GitHub.
Under the Source Code section in the Overview tab of a test run, click the View on GitHub button to view the relevant lines of code for that test within GitHub.
IDE plugins and extensions are required to view your test in your IDE.