Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove phrase on Cypress fetch support #1211

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Remove phrase on Cypress fetch support #1211

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/routes/docs/comparison-with-other-tools.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ Mirage recommends writing UI tests at a single level of abstraction, usually foc

These differences are just about Cypress' HTTP mocking layer though – overall, we're big fans of Cypress! And Mirage works great when used as the API mocking layer right alongside your Cypress testing code. In fact, <Link to='/quickstarts/cypress/'>we even have a Quickstart guide on getting Mirage set up in a Cypress app</Link>!

Other differences include the fact that Cypress' API mocks are typically not shared in development, which is a big part of Mirage's core value offering. Additionally, as of this writing, Cypress doesn't intercept `fetch` requests, whereas Mirage does.
Other differences include the fact that Cypress' API mocks are typically not shared in development, which is a big part of Mirage's core value offering.

---

Expand Down