Skip to content

Commit c236476

Browse files
committed
update doc
1 parent 4f6db12 commit c236476

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

README.md

+9-3
Original file line numberDiff line numberDiff line change
@@ -511,11 +511,11 @@ See casperjs documentation for more info on instance options. An example config
511511
```
512512

513513
### Setting Chromy option flags
514-
Chromy enables a lot of behavior via constructor options. See Chromy documentation for more info.
514+
Chromy enables a lot of behavior via constructor options. See Chromy documentation for more info.
515515

516516
**NOTE:** Backstop sets defaults for many Chromy properties. Setting a parameter value with engineOptions will override any default value set by backstop. _But please watch out for the following..._
517517
- (TLDR) Setting `port` is _very_ _very_ not advised.
518-
- Setting `chromeFlags` will override all chromeFlags properties set by backstop -- **EXCEPT FOR `--window-size`***... (i.e. `--window-size` flag will be added by backstop if not found in chromeFlags)
518+
- Setting `chromeFlags` will override all chromeFlags properties set by backstop -- **EXCEPT FOR `--window-size`***... (i.e. `--window-size` flag will be added by backstop if not found in chromeFlags)
519519
- Setting `--window-size` explicitly in `chromeFlags` will override values used in your viewport settings.
520520

521521

@@ -732,12 +732,18 @@ For all engines there is also the `debug` setting. This enables verbose console
732732
```
733733

734734

735-
### The dreaded: `Error: Failed to launch a browser.`
735+
### `Error: Failed to launch a browser.`
736736
Sometimes (usually after an app error) a chrome process is left open. If that's the case try...
737737
```
738738
pkill -f "(chrome)?(--headless)"
739739
```
740740

741+
### `Chromy error: Error. See scenario ...`
742+
Same as the above issue. If a zombie Chrome instance is blocking a port, you can run...
743+
```
744+
pkill -f "(chrome)?(--headless)"
745+
```
746+
741747
### The dreaded: _command-not-found_ error...
742748

743749
Did you install BackstopJS with the global option? If installing globally remember to add that `-g` when installing with npm *i.e.* `npm install backstop -g`. If you installed *locally*, remember that the `backstop <command>` pattern will only be available to your npm scripts -- see the local installation section above for more info.

0 commit comments

Comments
 (0)