Skip to content

quotes around --spec argument in examples #686

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 7, 2018
Merged

quotes around --spec argument in examples #686

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions source/guides/guides/command-line.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,19 +118,19 @@ cypress run --reporter-options mochaFile=result.xml,toConsole=true
### Run tests specifying a single test file to run instead of all tests

```shell
cypress run --spec cypress/integration/app.spec.js
cypress run --spec 'cypress/integration/app.spec.js'
```

### Run tests specifying a glob of where to look for test files

```shell
cypress run --spec cypress/integration/login/**/*
cypress run --spec 'cypress/integration/login/**/*' ## Note: quotes required
```

### Run tests specifying multiple test files to run

```shell
cypress run --spec cypress/integration/filter.spec.js,cypress/integration/users.spec.js
cypress run --spec 'cypress/integration/filter.spec.js,cypress/integration/users.spec.js'
```

### Run tests specifying a project
Expand Down
2 changes: 1 addition & 1 deletion source/guides/references/changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1512,7 +1512,7 @@ Fixed {% url "`.type()`" type %} not firing `input` event for {% url "React" htt

**Bugfixes:**

- The `-s` or `--spec` option now works correctly. You now must pass a relative or absolute path to your spec file. This is much less confusing, allows you to easily autocomplete entries from bash, and will support `unitFolder` later when it's added. Assuming you want to run a spec file that is located in `cypress/integration/foo_spec.js` you would pass: `cypress run --spec cypress/integration/foo_spec.js`. Previously you could just pass `--spec foo_spec.js` which now no longer works (and was broken anyway). Fixes {% issue 120 '#120' %}.
- The `-s` or `--spec` option now works correctly. You now must pass a relative or absolute path to your spec file. This is much less confusing, allows you to easily autocomplete entries from bash, and will support `unitFolder` later when it's added. Assuming you want to run a spec file that is located in `cypress/integration/foo_spec.js` you would pass: `cypress run --spec 'cypress/integration/foo_spec.js'`. Previously you could just pass `--spec foo_spec.js` which now no longer works (and was broken anyway). Fixes {% issue 120 '#120' %}.

**Misc:**

Expand Down