> For the complete documentation index, see [llms.txt](https://revdebug.gitbook.io/revdebug/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://revdebug.gitbook.io/revdebug/revdebug-features/tests-monitoring.md).

# Tests Monitoring

RevDeBug trace id can be included in Cypress error reports for easier root cause detection for failed automated end-to-end tests.

### Prerequisite

Installed and configured RevDeBug Node.JS module - please refer to [JavaScript section](/revdebug/supported-langauges/javascript.md).

### Usage

From command line at the cypress project root directory add a reference to the @revdebug module repository:

```
npm config set @revdebug:registry https://nexus.revdebug.com/repository/npm/
```

Then install RevDeBug Cypress plugin:

```
npm install @revdebug/cypress-plugin-revdebug
```

The last step is to add to `cypress/support/index.js` file at bottom:

```javascript
require('@revdebug/cypress-plugin-revdebug')
```

### Expected results

Failed automated tests will report "**RevDeBug trace**" at the top of the error message as shown below. The trace id can be used to locate transactions at "**Trace**" tab at RevDeBug web interface and access detailed frontend and backend code execution recordings.

![Last failed request trace id appended to Cypress error message.](https://1776828725-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MTk4m0D_HMejz7b-sEi%2F-MX2ziGU_zL_BRi5AqYq%2F-MX301U4-xJDvIhE6dft%2Fimage.png?alt=media\&token=748a1773-31c3-4f85-bb9c-45f035a0dc20)

![The same trace id visible from RevDeBug web interface with detailed recording of whole transaction available to the developer.](https://1776828725-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MTk4m0D_HMejz7b-sEi%2F-MX6ZeIiVTAtubU0S88X%2F-MX74ss6xAqmvCVseujz%2Fimage.png?alt=media\&token=eda3187d-e3a2-4fdb-aa2b-05b369544b6c)