mirror/cypress
1
0
Fork 0
mirror of https://github.com/cypress-io/cypress.git synced 2026-02-20 06:01:12 -06:00
Code Issues Packages Projects Releases Wiki Activity

fix menuspy fail found by spider

Browse Source
This commit is contained in:
Loren Norman
2017-06-02 18:00:22 -04:00
parent a05a81612f
commit df6efa137a
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/source/guides/cypress-basics/dealing-with-the-network.md
View File

@@ -32,7 +32,7 @@ Let's investigate both strategies, why you would use one versus the other, and w
***
## 1: Don't Stub Responses
## Option 1: Don't Stub Responses
Requests that aren't stubbed will actually reach your server. By *not* stubbing your responses, you are writing true **end to end** tests. This means you are driving your application the same way a real user would.
@@ -67,7 +67,7 @@ If you are writing a traditional server-side application where most of the respo
***
## 2: Stub Responses
## Option 2: Stub Responses
Stubbing responses enables you to control every aspect of the response, including the response body, the status, headers, and even network delay. Stubbing is extremely fast, most responses will be returned in less than 20ms.