- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
This page provides information to help you troubleshot issues with Test Impact Analysis. If you need additional help, contact Datadog Support.
Test Impact Analysis works by analyzing your commit history along with code coverage information about past test runs to determine which tests need to be run and which ones can be safely skipped. A minimum amount of information needs to exist in order for Test Impact Analysis to work correctly:
git
executable needs to be available in the host running tests.git clone --depth=1
), but that might not work on older versions of git. Automatic unshallowing might require additional set up in some CI providers (Harness CI, for example, requires extra configuration to make sure your pipeline can execute git commands). If your CI job is using shallow git clones, you can change it to use partial git clones by using the following command: git clone --filter=blob:none
.Due to these restrictions, the first time you enable Test Impact Analysis, you cannot see any tests skipped and the test execution time may be slower than usual because the code coverage is collected automatically.
Test Impact Analysis only takes into account the commit history and test code coverage information for the past month. Additionally, it does not take into account code coverage information that is generated more than one week after a commit was made.
Synchronizing a fork through GitHub’s UI causes all tests to be run for the generated synchronization commit.
Tests run in GitHub Actions CI using the pull_request
trigger may not be skipped on subsequent commits within the pull request’s branch. The trigger introduces changes using a new merge commit that is not considered by Test Impact Analysis.
Using squash and merge to integrate commits into the base branch causes the git history of the feature branch to be lost. As a result, Test Impact Analysis may not skip tests in the base branch that were recently skipped in the feature branch.
Test Impact Analysis performs test impact analysis based on code coverage to determine which tests are impacted by a given commit or set of commits. While this strategy works for the majority of tests, there are known scenarios where Test Impact Analysis could skip a test that should have been run:
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.
추가 유용한 문서, 링크 및 기사: