---
title: Test Mode - Canvas
description: Run your integration in test mode before deploying it to the environment
documentId: ipaas-legacy-test-mode
locale: en-US
---

Test mode allows you to execute an integration flow before its deployment to the environment.
It offers benefits such as error detection, data validation, and performance optimization, ensuring that the integration works correctly.
Additionally, it is possible to test a flow even if it is not yet complete, allowing adjustments and improvements throughout the process.

**Requirements for test mode execution:**

* All mandatory information in the configuration forms must be filled in;
* The flow must include a trigger *step*;
* The flow must be saved before test execution;
* All *steps* must be connected;
* If the flow uses environment variables, the test will be executed with the values defined in the [environment variables](/docs/integrations/ipaas-legacy-variables).
* If the flow you created uses authorizations, you must register the authorization in the **Staging** environment.

<Callout type="important" title="IMPORTANT">
Test mode should be used for basic validations during flow creation.
For tests involving large data volumes, we recommend deploying the flow to a staging environment, when appropriate.
</Callout>

![test-mode-button.gif](https://creative-ball-51b3fc85c0.media.strapiapp.com/test_mode_button_3223e95a1e.gif)

## Configuring test mode

Test mode configuration depends on the **trigger type** you are using.
There are two types of triggers:

* [REST](#rest-trigger)
* [Scheduler](#scheduler-trigger)

Next, learn how to configure the execution information for each type.

### REST

<Steps>
  <Step>
  Click the **TEST MODE** button in the upper right corner.
  </Step>
  <Step>
  (Optional) On the **Test Mode** screen, fill in the following fields:
  
  * **Body**: insert the *payload* for execution.
  * **Headers**
    * **Name**: enter a name for the *Header* value. Maximum of 40 characters.
    * **Value**: enter the value.
    
    To add new values, click the ![](https://creative-ball-51b3fc85c0.media.strapiapp.com/more_Icon_01c57e0f48.png) button.
    
  * **Query Params**
    * **Name**: enter a name for the *Query Params* value.
    * **Value**: enter the value.
    
    To add new values, click the ![](https://creative-ball-51b3fc85c0.media.strapiapp.com/more_Icon_01c57e0f48.png) button.
    
  <Callout type="tip" title="TIP">
  To expand or hide field values above, click on the arrow icon ![down arrow icon](https://creative-ball-51b3fc85c0.media.strapiapp.com/expand_Icon_9d4d07a008.png).
  You can also use scrolling if you want to view all three fields expanded.
  
  The ![green check](https://creative-ball-51b3fc85c0.media.strapiapp.com/check_circle_ff7a17fabb.png) sign indicates that the fields have been filled in.
  </Callout>
  </Step>
  <Step>
  Click the **EXECUTE** button.
  </Step>
  <Step>
  Check the execution response right below, in [Execution Info](#execution-info).
  </Step>
</Steps>

![test-mode-rest-trigger.png](https://creative-ball-51b3fc85c0.media.strapiapp.com/test_mode_rest_trigger_59a46e8cb4.png)

### Scheduler

<Steps>
  <Step>
  Click the **TEST MODE** button in the upper right corner.
  
  On the **Test Mode** screen, the **Body**, **Headers**, and **Query Params** fields are blocked for this trigger.
  </Step>
  <Step>
  Click the **EXECUTE** button.
  </Step>
  <Step>
  Check the execution response right below, in [Execution Info](#execution-info).
  </Step>
</Steps>

![test-mode-scheduler-trigger.png](https://creative-ball-51b3fc85c0.media.strapiapp.com/test_mode_scheduler_trigger_54afb45573.png)

## Execution information

The **Execution Info** section displays details of the integration flow execution.
Here, you can check:

* **Execution Status**: the execution status.
Can be *deploying* (executing), success, or error.

* **Execution ID**: the execution identification.

* **Start Time**: date and time of execution start.

* **End Time**: date and time of execution end.

* **Duration**: the total test execution time in milliseconds.

* **View Log** ![width=24px, height=24px](https://creative-ball-51b3fc85c0.media.strapiapp.com/open_in_new_Icon_4201b7f235.png): by clicking this button, you can view detailed execution logs in [**Sensedia Analytics**](https://docs.sensedia-eng.com/pt-BR/docs/analytics).

<Callout type="note" title="NOTE">
Integration execution in test mode **does not** generate logs on the [**Executions**](/docs/integrations/ipaas-observability-monitoring) screen.
</Callout>

![execution-info.png](https://creative-ball-51b3fc85c0.media.strapiapp.com/execution_info_31fccf4d1f.png)

<Callout type="tip" title="TIP">
Better understand the format of [execution logs](/docs/integrations/ipaas-logs) displayed in Sensedia Analytics.
</Callout>