You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-3
Original file line number
Diff line number
Diff line change
@@ -511,11 +511,11 @@ See casperjs documentation for more info on instance options. An example config
511
511
```
512
512
513
513
### 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.
515
515
516
516
**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..._
517
517
- (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)
519
519
- Setting `--window-size` explicitly in `chromeFlags` will override values used in your viewport settings.
520
520
521
521
@@ -732,12 +732,18 @@ For all engines there is also the `debug` setting. This enables verbose console
732
732
```
733
733
734
734
735
-
### The dreaded: `Error: Failed to launch a browser.`
735
+
### `Error: Failed to launch a browser.`
736
736
Sometimes (usually after an app error) a chrome process is left open. If that's the case try...
737
737
```
738
738
pkill -f "(chrome)?(--headless)"
739
739
```
740
740
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
+
741
747
### The dreaded: _command-not-found_ error...
742
748
743
749
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