# Tests Monitoring

### 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.](/files/-MX301U4-xJDvIhE6dft)

![The same trace id visible from RevDeBug web interface with detailed recording of whole transaction available to the developer.](/files/-MX74ss6xAqmvCVseujz)


---

# 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://revdebug.gitbook.io/revdebug/revdebug-features/tests-monitoring.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.