Test mode

Learn about the Digibee Platform Test mode functionality

Gabrielly Pereira avatar
Written by Gabrielly Pereira
Updated over a week ago

IMPORTANT: this documentation has been discontinued. Read the updated Test mode documentation on our new documentation portal.

Test mode is a feature of the Digibee Platform that is commonly used when building pipelines, as it provides a way to run and test the pipeline directly from your development area. It is often used to evaluate implementation logic, debug and troubleshoot integrations before deploying the pipeline to production.

Initial information

Test mode runs the pipeline in the test environment. That is, we use the Digibee Platform test environment to run your pipeline and validate the integration logic. In addition, Test mode uses test values registered in the Globals, Accounts, Relationship, and Multi-Instance services.

IMPORTANT: Depending on the amount of data transactions to be executed, the message "Out of memory" may be displayed in test mode.

How can you test your pipeline using test mode?

Test tab

On the TEST tab, you can enter input data in the left column to run the test, click "RUN" and view the execution result in the output payload (right column).

For instance, the REST V2 component, which makes HTTP endpoint calls, allows users to search and query web services databases like ViaCEP. The input "cep": 22460050 resulted in an output payload providing information about the input data in the example above.

Multi-instance pipelines

If the pipeline you want to run is multi-instance, you can specify the instance you want to run in the first column of the TEST tab, as in the following example:

In this way, the Test mode uses the data of the selected instance to proceed with the execution.

Logs tab

The LOGS tab contains information about the event logs that occur during the execution of a pipeline in Test mode, and allows visualization of individual logs in a dedicated section. The information from each log is organized in the report according to the following columns:

  • Timestamp: The date and time the step was executed in the pipeline;

  • Log level: The classification of the log, i.e. its level, can be:

    • INFO: Informative logs;

    • ERROR: Logs that presented an error during execution;

    • WARN: Logs that contain a warning.

  • Log message: The messages in each log, i.e. the event’s records concerning the execution of the pipeline.


It is possible to copy the details of a particular log using the Copy Button option located in Actions.

“View more logs” button

If you click on the "See more logs" button, more logs will be loaded and can be viewed.

Messages tab

In this tab, you can view the pipeline execution messages. Each message displayed refers to the result of the execution of the respective component. A component always receives the payload generated by the previous component, processes that payload based on its function, and generates a new payload in response. However, only the first 50 pipeline steps will be shown when it is run in Test mode.

You can copy a specific message to the clipboard by using the button in the upper right corner of each block.

“Update” button

By clicking on “Update”, the entire content of this tab is updated, bringing more messages from the executed pipeline.

Additional Information


  • To open or close Test mode : ctrl+D; command + D.

  • To run Test mode: ctrl + Enter; command + Enter.

Did this answer your question?