> For the complete documentation index, see [llms.txt](https://docs.deepomatic.com/platform-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deepomatic.com/platform-documentation/deepomatic-drive/configuring-visual-automation-applications/assembling-workflows/workflow-testing/workflow-regression-testing.md).

# Workflow regression testing

Utilize the `wf_client regression` command to run the analyses on the work orders from production.

**Example of the command:**

```css
wf_client regression --org circet-ireland --solution_id 4595e77a-6bf9-4637-9be0-820dd5f18301 --site_name 'Smart meters - testing' --number 30 --to-json input.json --cwd /home/me/projects/missions/...
```

**You can specify the parameters as needed:**

* Organization: `--org your-organization`
* Solution ID: `--solution_id your-id`
* Site Name: `--site_name 'site-name'`
* Number of WOs: `--number 300`
* Create an `input.json` file with the corrupted task group names and entries: `--to-json input.json`
* Absolute path to the project’s folder: `--cwd /home/me/projects/missions/path-to-the-project`

{% hint style="info" %}
Note that only work orders with the inputs will be considered. Therefore, the final count of analyzed work orders may be less than initially specified.
{% endhint %}

During the execution process, inputs will be saved to a new folder, created after every command launch: `your-project-path/regression_tests/regression_test_date/` . The `input.json` file will be saved to the same folder.

If errors occur during the analysis, they will be displayed in the terminal at the end of the execution process.

{% hint style="warning" %}
As we are using work orders selected from the Search Dashboard, it is necessary to add `site_name` as a facet/filter in the Algolia Search before.
{% endhint %}