> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getoperate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Instant Preview & Testing

> On top of its integrated editors (scripts, flows, apps), getOperate allows users to see and test what they are building directly from the editor, even before deployment.

## Instant preview in Script Editor

The right margin of the script editor displays:

1. The inputs of the main function, which are parsed to create an auto-generated UI.
2. The logs and results of the last execution.
3. The history of the latest runs via the editor.

<Card title="Script Editor">
  Scripts are the basic building blocks that can be written in Typescript, Python, Go, Bash, SQL or launch docker containers.
</Card>

### VS Code Extension

For users on [VS Code Extension](#), you can also preview instantly and test with the `getOperate: Run preview` command.

<Card title="VS Code Extension">
  Build scripts and flows in the comfort of your VS Code Editor, while leveraging getOperate UIs for test & flows edition.
</Card>

## Instant preview in Flow Editor

The flow editor has several methods of previewing results instantly.

Testing the flow or certain steps is often required to have the outputs of previous steps suggested as input for another step:

<Card title="Flow Editor">
  getOperate's Flow Editor allows you to build flows with a low-code builder.
</Card>

### Test flow

While editing the flow, you can run the whole flow as a test.

Click on `Test flow`. This will open a drawer with the [flow's inputs](#) and its status.

Upon execution, you can graphically preview (as a directed acyclic graph) the execution of the flow & the results & logs of each step.

From the menu, you can also access past runs & saved inputs.

At last, you can fill arguments from a request.

### Test up to step

As for `Test flow`, you will get the same components (Flow inputs, status, input library etc.), only the flow will execute until a given step, included.

### Restart from step, iteration or branch

Restart a flow at any given top level step. For-loop and branch-all can be restarted at a specific iteration/branch.
In the flow preview page, just select a top level node and a "Re-start from X" button will appear at the top, next to "Test flow".

To see how it works, see our [dedicated blog post](#).

Under [enterprise edition](#), this feature is also available for [deployed](#) flows.

### Test this step

`Test this step` is a way to test a single step of the flow. It comes useful to check your code or to have the results of your current steps suggested as inputs for further steps.

The arguments are pre-filled from the step inputs (if the arguments use results from previous steps, they will be used if those were tested before), but you can change them manually.

## Instant preview in App Editor

The app editor has several methods of previewing results instantly.

<Card title="App Editor">
  The app editor is where you build an app with components, create interactions with runnables (scripts & flows), and configure the app settings.
</Card>

### Run manually a runnable

When on a runnable from the [runnable panel](#), you can manually run it.

### Run all

On the top bar of the app, you can either manually run all runnables of set a given run frequency.

### Preview

The [preview mode](#) of the app will run all runnables before previewing them.