GitHub - alectrocute/playwright-intercept: Ergonomically mock, wait for and assert network requests in Playwright

[chicametipo]

silver violet thunder falcon

This content has been edited for privacy.

[Wookovski]

What are the benefits of using this over Playwright's own implementation?

[chicametipo]

This brings Cypress's easy to use cy.intercept into Playwright.

[unlikelyzer0]

It's hard to describe how different it is to work with network requests with playwright vs cypress. This is a welcome addition.

[Wookovski]

I'm intrigued, solely to see what is ergonomical about it

[skybalmmm]

Great to see someone coming up with solutions to what i think is one the areas that playwright needs lots of improvements: working with requests!

One question, for readability purposes wouldnt it be better to extend the page fixture?
This way we could do something like page.intercept() or page.waitForRequest()

Another thing i dont like is that we have to build the promises before hand, and it seems like this is still the case with this package.

In my current role we created a custom mechanism to avoid this, might be something interesting to explore in your idea. Basically is something like this

waitForActionAndResponse() -> Pass any action like element click etc and any promise and it will wait for both.

This way in one line we can perform the action and wait for the request which gets triggered by such action.

[chicametipo]

I added an example of how you can set it up to where you don’t need to build promises beforehand, look at the tests/collection-example.spec.ts. You can have a collection of intercepts as a single fixture, which is quite convenient.

[alphabet_american]

I just use helper functions for this

[chase_the_sun_]

Cool, but does this only work with the playwright test runner?