cypress/docs/source/api/commands/exec.md

---
title: exec
comments: false
---

Execute a system command.

{% note warning 'Web Server Processes' %}
We do NOT recommend trying to start your backend web server from within Cypress.

`cy.exec()` can only run commands which eventually exit.

Trying to start a web server from `cy.exec()` causes all kinds of problems because:

- You have to background the process
- You lose access to it via terminal
- You don't have access to its `stdout` or logs
- Every time your tests run, you'd have to work out the complexity around starting an already running web server.
- You would likely encounter constant port conflicts

**Why can't I shut down the process in an `after` hook?**

Because there is no guarantee that code running in an `after` will always run.

While working in the Cypress GUI you can always restart / refresh while in the middle of a test. When that happens, code in an `after` won't execute.

**What should I do then?**

Simple. Start your web server before running Cypress. That's it!
{% endnote %}

# Syntax

```javascript
cy.exec(command)
cy.exec(command, options)
```

## Usage

**{% fa fa-check-circle green %} Correct Usage**

```javascript
cy.exec('npm run build')    
```

## Arguments

**{% fa fa-angle-right %} command** ***(String)***

The system command to be executed from the project root (the directory that contains `cypress.json`).

**{% fa fa-angle-right %} options** ***(Object)***

Pass in an options object to change the default behavior of `cy.exec()`.

Option | Default | Description
--- | --- | ---
`log` | `true` | {% usage_options log %}
`env` | `{}` | Object of environment variables to set before the command executes (e.g. `{USERNAME: 'johndoe'}`). Will be merged with existing system environment variables
`failOnNonZeroExit` | `true` | whether to fail if the command exits with a non-zero code
`timeout` | {% url `execTimeout` configuration#Timeouts %} | {% usage_options timeout cy.exec %}

## Yields {% helper_icon yields %}

`cy.exec()` yields an object with the following properties:
- `code`
- `stdout`
- `stderr`

# Examples

## Prepping data

`cy.exec` provides an escape hatch for running arbitrary system commands, so you can take actions necessary for your test outside the scope of Cypress. This is great for:

- Running build scripts
- Seeding your test database
- Starting processes
- Killing processes

**Run a build command**

```javascript
cy.exec('npm run build').then(function (result) {
  // yields the 'result' object
  // {
  //   code: 0,
  //   stdout: "Files successfully built",
  //   stderr: ""
  // }
})
```

**Seed the database and assert it was successful**

```javascript
cy.exec('rake db:seed').its('code').should('eq', 0)
```

**Run an arbitrary script and assert its output**

```javascript
cy.exec('npm run my-script').its('stdout').should('contain', 'Done running the script')
```

**Write to a file to create a fixture from response body**
```javascript
cy.server()
cy.route('POST', '/comments').as('postComment')
cy.get('.add-comment').click()
cy.wait('@postComment').then(function(xhr){
  cy.exec(`echo ${JSON.stringify(xhr.responseBody)} >cypress/fixtures/comment.json`)
  cy.fixture('comment.json').should('deep.eq', xhr.responseBody)
})
```

## Options

**Change the timeout**

You can increase the time allowed to execute the command, although *we don't recommend executing commands that take a long time to exit*.

Cypress will *not* continue running any other commands until `cy.exec()` has finished, so a long-running command will drastically slow down your test cycle.

```javascript
// will fail if script takes longer than 20 seconds to finish
cy.exec('npm run build', { timeout: 20000 });
```

**Choose to not fail on non-zero exit and assert on code and stderr**

```javascript
cy
  .exec('man bear pig', { failOnNonZeroExit: false })
  .its('code').should('eq', 1)
  .its('stderr').should('contain', 'No manual entry for bear')
```

**Specify environment variables**

```javascript
cy
  .exec('echo $USERNAME', { env: { USERNAME: 'johndoe' } })
  .its('stdout').should('contain', 'johndoe')
```

# Notes

**Commands that do not exit are not supported**

`cy.exec()` does not support commands that don't exit, such as:

- Starting a `rails server`
- A task that runs a watch
- Any process that needs to be manually interrupted to stop

A command must exit within the `execTimeout` or Cypress will kill the command's process and fail the current test.

# Rules

## Requirements {% helper_icon requirements %}

{% requirements exec cy.exec %}

## Assertions {% helper_icon assertions %}

{% assertions once cy.exec %}

## Timeouts {% helper_icon timeout %}

{% timeouts exec cy.exec %}

# Command Log

**List the contents of cypress.json**

```javascript
cy.exec('cat cypress.json')
```

The command above will display in the command log as:

![Command Log exec](/img/api/exec/exec-cat-in-shell.png)

When clicking on the `exec` command within the command log, the console outputs the following:

![console.log exec](/img/api/exec/console-shows-code-shell-stderr-and-stdout-for-exec.png)

# See also

- {% url `cy.readFile()` readfile %}
- {% url `cy.request()` request %}
- {% url `cy.writeFile()` writefile %}