Stopping the Flake: Controlling Network State with cy.intercept()
Learn how to eliminate flaky E2E tests by using cy.intercept() to stub network requests, manage API state, and synchronize your UI assertions with network behavior.
Loading…
ReadMeFeed / Community knowledge
#network-stubbing
Real questions. Useful conversations. Find the people who know your stack.
cypressio
javascriptHandling Asynchronous Network Requests with cy.intercept()
Learn how to eliminate flaky tests in Cypress using cy.intercept() to stub network requests, handle asynchronous responses with aliases, and simulate server errors.
Stubbing API Responses in Cypress with cy.intercept
Learn how to control HTTP requests in Cypress tests with cy.intercept, see a worked example of stubbing a GET endpoint, and understand the trade-offs of over-stubbing.
Using Cypress.io cy.intercept to Stub Network Requests Reliably
Learn how to use Cypress.io's cy.intercept to stub network requests, isolate frontend tests, and avoid flaky CI builds.
Make Cypress End‑to‑End Tests Reliable with cy.intercept
Flaky network calls in Cypress tests? Use cy.intercept to mock, spy on, or modify HTTP traffic, turning flaky, data‑dependent checks into deterministic, fast tests. Learn how, when, and where to apply it effectively.
Stopping the Flake: Using cy.intercept() to Decouple Frontend Tests from Backend State
Learn how to use cy.intercept() in Cypress to eliminate flaky tests by stubbing network responses and simulating edge cases like 500 errors and network latency.
Stop Stubbing Blindly: Getting Real Value from Cypress cy.intercept()
Fixed cy.wait(ms) delays are the top cause of flaky Cypress suites. Learn how cy.intercept() with aliased routes fixes timing, enables deterministic stubbing, and where its limits are.
cy.intercept auto‑cleanup: Does Cypress clear intercepts between test cases by default?
Background In Cypress, cy.intercept is commonly used to stub or monitor network requests during tests. The official documentation states that intercepts are automatically cleared after each test case unless explicitly cleared earlier. However, many developers wish for intercepts to persist across multiple tests to avoid redefining identical stubs, and the Cy
cy.intercept() network capture timing during before() hooks
Testing frontend integrations without production credentials requires stubbing network requests using cy.intercept() . This ensures that sensitive API endpoints are not called and prevents side effects in production environments. A specific design concern arises regarding the execution order of the Cypress lifecycle. When cy.intercept() is defined within a b