> For the complete documentation index, see [llms.txt](https://docs.devtodev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devtodev.com/integration/test-devices.md).
# Test Devices
In devtodev you can mark a device as a test device. You can do so in the [Users & Segments](/reports-and-functionality/project-related-reports-and-fuctionality/users.md#mark-as-cheater-or-tester) section or in Settings -> SDK -> [Test Devices](/reports-and-functionality/project-related-reports-and-fuctionality/settings.md#test-devices).
The system will exclude from the reports all incoming events from the test devices (except Real-time dashboard). You can check the evets in Settings -> SDK -> Integration -> [Event Log](/reports-and-functionality/project-related-reports-and-fuctionality/settings.md#event-log) or in the Users & Segments section.
When you mark the User card as a Tester, the log in the User card will not be cached and the events will appear much quicker.
If the app is in test mode, all devices with this app are added automatically to the list of test devices (up to 100 users). You can switch to Production mode manually in Settings -> [General Settings](/reports-and-functionality/project-related-reports-and-fuctionality/settings.md#switch-to-production-mode).
## Users & Segments
In the [Users & Segment](/reports-and-functionality/project-related-reports-and-fuctionality/users.md) section you can find a specific user using filters. For example, search a specific Advertisig ID or IDFA.
Open the User Card and mark the User as a Tester.
## Test Devices
You can check and configure your list of test devices in Settings -> SDK -> [Test Devices](/reports-and-functionality/project-related-reports-and-fuctionality/settings.md#test-devices).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.devtodev.com/integration/test-devices.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
