Skip to content
This repository was archived by the owner on Mar 29, 2023. It is now read-only.

Commit e3cfc39

Browse files
committed
add note about the config object
1 parent 30df327 commit e3cfc39

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed

README.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -407,6 +407,18 @@ Cypress.grep('hello', '@smoke', 10)
407407

408408
## Debugging
409409

410+
When debugging a problem, first make sure you are passing the values to the plugin correctly by inspecting the "Settings" tab in the Cypress Desktop GUI screen. You should see the values you have passed in the "Config" object under the `env` property. For example, if I start the Test Runner with
411+
412+
```text
413+
$ npx cypress open --env grep=works,grepFilterTests=true
414+
```
415+
416+
Then I expect to see the grep string and the "filter tests" flag in the `env` object.
417+
418+
![Values in the env object](./images/config.png)
419+
420+
### Log messages
421+
410422
This module uses [debug](https://github.com/visionmedia/debug#readme) to log verbose messages. You can enable the debug messages in the plugin file (runs when discovering specs to filter), and inside the browser to see how it determines which tests to run and to skip.
411423

412424
### Debugging in the plugin

images/config.png

230 KB
Loading

0 commit comments

Comments
 (0)