# 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.

![](https://3071851461-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4Nnmtk9_gFGWOddsf6%2F-MNJ-Ik4o8-wuUcCPhmx%2F-MNJ3O7NzIcw9f9q8Pkb%2Ftest1.gif?alt=media\&token=fcd3f9a5-bd41-4abb-a9ae-ed97a320ea8e)

{% 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

![](https://3071851461-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4Nnmtk9_gFGWOddsf6%2F-MNJ-Ik4o8-wuUcCPhmx%2F-MNJ6RZMlt181c_T2dYb%2Ftest2.gif?alt=media\&token=a2610c7c-65ed-4ca6-8566-87ad0d797ebb)

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

![](https://3071851461-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4Nnmtk9_gFGWOddsf6%2F-MNJ-Ik4o8-wuUcCPhmx%2F-MNJ7-wUSF9pKIgE5OCw%2Ftest1.png?alt=media\&token=2e1ea6db-a182-4f5d-a2bd-850a8501acbb)

## Testing option 3. Throwing objects into scenario

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

![](https://3071851461-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4Nnmtk9_gFGWOddsf6%2F-MNJ-Ik4o8-wuUcCPhmx%2F-MNJAA6kzViMxENJGetP%2Ftest3.gif?alt=media\&token=79287a04-0e0a-4d8f-9a88-c23433cd1dd1)

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 %}