- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
This page describes advanced options for Synthetic mobile app tests.
To ensure that your mobile app test does not validate an unexpected change to your mobile application’s UI, use assertions in your test creation. Assertions allow you to define what is and what is not expected behavior associated with the test step journey.
By default, mobile app tests use the Datadog locator system. When a test searches for a specific element to interact with (for example, a checkout button), instead of looking at an element with a specific XPath or a specific CSS selector, the test uses several different points of reference to locate the element (for example, XPath, text, classes, and nearby elements).
These points of reference become a set of locators, each of which uniquely define the element. You should only use custom selectors in edge cases because the Datadog locator system enables tests to be self-maintaining.
Custom selectors are created by performing a step in the recorder (such as a tap, double tap, or open deep link) on any element of your page. This specifies the kind of step that needs to be performed.
Optionally, under advanced options, use handlebars ({{) syntax to insert dynamic content. A pre-populated dropdown list of variables is shown:
If a mobile app test cannot locate an element, it retries the step for 60 seconds by default.
You can customize this timeout up to 60 seconds if you want your test to wait for less time to be able to find the step targeted element.
In some cases, such as in the event of a pop-up, you may want to make some steps optional. To configure this option, select Continue with test if this step fails. If the step fails after the amount of minutes specified on the timeout option, then the mobile app test moves on and executes the next step.
Optionally, click Consider entire test as failed if this step fails to ensure important steps are performing.
You can prevent a step screenshot from being captured at test execution by clicking Do not capture screenshot for this step.
This is helpful to ensure no sensitive data gets featured in your test results. Use mindfully as it can make failure troubleshooting more difficult. For more information, see Synthetic Monitoring Data Security.
Configure this option to exit the test after a successful step completion. This prevents running unnecessary steps and avoids marking the test as a failure.
The advanced options for subtests allow you to set the behavior of your mobile app test if the subtest fails.
Click Continue with test if this step fails to ensure your mobile app test continues if the subtest fails.
| |
