> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/new-alarms/configuration/test-mode-in-new-alarms.md).

# Test Mode in New Alarms

Test Mode allows you to test your alarm devices and confirm that your system is set up correctly without triggering a monitored response. It is typically used after installing or servicing the system.

***

## Enable Test Mode

{% hint style="danger" %}
You need Site Admin permissions to enable Test Mode.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Alarms.**
{% endstep %}

{% step %}
**Select the alarm site where you want to perform the test.**
{% endstep %}

{% step %}
**On the left, click System Status.**

1. In the top right, select **Tests.**
2. From the dropdown, select **Enable Test Mode.**
3. Arm the appropriate partition and trigger the devices you want to test. Confirm that the expected alarms and notifications are generated, then disarm the partition.
4. In the top right, select **End Test** to disable Test Mode. 
   {% endstep %}
   {% endstepper %}

{% hint style="info" %}
When Test Mode is enabled:

* All partitions at the site are placed in Test Mode.
* Alarm monitoring is disabled. Monitoring agents will not verify activity, contact response contacts, or request emergency dispatch.
* You will continue to receive alarm notifications.
* Test Mode does not end automatically. You must manually select **End Test** in Verkada Command when testing is complete.
  {% endhint %}


---

# 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://help.verkada.com/new-alarms/configuration/test-mode-in-new-alarms.md?ask=<question>&goal=<user_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.