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: source/guides/overview/key-differences.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ Having ultimate control over your application, the network traffic, and native a
37
37
- Test how your application responds to errors on your server by {% url "modifying response status codes to be 500" route %>.
38
38
- Modify DOM elements directly - like forcing hidden elements to be shown.
39
39
- Use 3rd party plugins programmatically. Instead of fussing with complex UI widgets like multi selects, autocompletes, drop downs, tree views or calendars, you can call methods directly from your test code to control them.
40
-
- <% url "Prevent Google Analytics from loading *before* any of your application code executes" configuration#blacklistHosts %> when testing.
40
+
- <% url "Prevent Google Analytics from loading *before* any of your application code executes" configuration#blockhosts %> when testing.
41
41
- Get synchronous notifications whenever your application transitions to a new page or when it begins to unload.
42
42
- {% url "Control time by moving forward or backward" clock %} so that timers or polls automatically fire without having to wait for the required time in your tests.
43
43
- Add your own event listeners to respond to your application. You could update your application code to behave differently when under tests in Cypress. You can control WebSocket messages from within Cypress, conditionally load 3rd party scripts, or call functions directly on your application.
Copy file name to clipboardExpand all lines: source/guides/references/configuration.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ Option | Default | Description
77
77
Option | Default | Description
78
78
----- | ---- | ----
79
79
`chromeWebSecurity` | `true` | Whether to enable Chromium-based browser's Web Security for same-origin policy and insecure mixed content. {% url 'Read more about Web Security' web-security %}.
80
-
`blacklistHosts` | `null` | A String or Array of hosts that you wish to block traffic for. {% urlHash 'Please read the notes for examples on using this.' blacklistHosts %}
80
+
`blockHosts` | `null` | A String or Array of hosts that you wish to block traffic for. {% urlHash 'Please read the notes for examples on using this.' blockHosts %}
81
81
`firefoxGcInterval` | `{ "runMode": 1, "openMode": null }` | Controls whether Cypress forces Firefox to run garbage collection (GC) cleanup and how frequently. During {% url "`cypress run`" command-line#cypress-run %}, the default value is `1`. During {% url "`cypress open`" command-line#cypress-open %}, the default value is `null`. See full details {% urlHash "here" firefoxGcInterval %}.
82
82
`modifyObstructiveCode` | `true` | Whether Cypress will search for and replace obstructive JS code in `.js` or `.html` files. {% urlHash 'Please read the notes for more information on this setting.' modifyObstructiveCode %}
83
83
`userAgent` | `null` | Enables you to override the default user agent the browser sends in all request headers. User agent values are typically used by servers to help identify the operating system, browser, and browser version. See {% url "User-Agent MDN Documentation" https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent %} for example user agent values.
@@ -258,7 +258,7 @@ When you open a Cypress project, clicking on the **Settings** tab will display t
258
258
259
259
# Notes
260
260
261
-
## `blacklistHosts`
261
+
## blockHosts
262
262
263
263
By passing a string or array of strings you can block requests made to one or more hosts.
264
264
@@ -307,7 +307,7 @@ For instance given a URL: `https://google.com/search?q=cypress`
307
307
- {% fa fa-exclamation-triangle red %} Does NOT match `*.google.com`
308
308
{% endnote %}
309
309
310
-
When Cypress blocks a request made to a matching host, it will automatically send a `503` status code. As a convenience it also sets a `x-cypress-matched-blacklist-host` header so you can see which rule it matched.
310
+
When Cypress blocks a request made to a matching host, it will automatically send a `503` status code. As a convenience it also sets a `x-cypress-matched-blocked-host` header so you can see which rule it matched.
311
311
312
312
{% imgTag /img/guides/blocked-host.png "Network tab of dev tools with analytics.js request selected and the response header highlighted " %}
313
313
@@ -394,7 +394,9 @@ Run GC cleanup before every 3rd test during {% url "`cypress run`" command-line#
394
394
IntelliSense is available for Cypress while editing your configuration file. {% url "Learn how to set up Intelligent Code Completion." IDE-integration#Intelligent-Code-Completion %}
395
395
396
396
{% history %}
397
-
{% url "3.5.0" changelog %} | Added support for option `nodeVersion`
397
+
{% url "5.0.0" changelog %} | Renamed `blacklistHosts` to `blockHosts`
0 commit comments