# Testing and Debugging

## Testing option 1. Checking the expression

When you compose an expression using object fields, you can check it on the go, providing an object ID to deal with.

![](/files/-MNJ3O7NzIcw9f9q8Pkb)

{% hint style="warning" %}
Remember, that "Checking the expression" shows the result expression in the text area, not the step result!
{% endhint %}

## Testing option 2. Checking the step

If you want to check a particular step, but not the entire scenario, you can use step testing

![](/files/-MNJ6RZMlt181c_T2dYb)

Moreover, if you use [Context variables](/scenarios/using-variables/context-variables.md), you can specify their values while testing:

![](/files/-MNJ7-wUSF9pKIgE5OCw)

## Testing option 3. Throwing objects into scenario

You can test the whole scenario by throwing an object in it.

![](/files/-MNJAA6kzViMxENJGetP)

Discover the test results in object or in logs.

{% hint style="info" %}
Remember, that you can use scenario testing both for *Running mode* and *Editing mode*. Sometimes such a mechanism is useful not for testing, but for manual scenario execution.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://readme.directual.com/scenarios/testing-and-debugging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.