attempting to recurse an api call using cy.waitUntil() and we had the brilliant idea of using the property called `status `that gives us the go or no go however when i attempt to do something like so

cy.waitUntil(
            () => {
                cy
                    .request({
                        method: 'GET',
                        headers: {
                            'token': accessToken
                        },
                        url: `api/is-ready`,
                        failOnStatusCode: false
                    }).its('status').should('eq', 'READY');

                    assertexpected 200 to equal **READY**

is there a way to access my 'status' and not the actual status code

check out http://github.com/bahmutov/cypress-recurse You can do anything you want with it

haha yea that was my next option thanks my man!

thanks that worked perfectly, shoulda used it the 1st time 😄

I have a test which makes a request to each of the links within a specific section of my page. I am trying to intercept the request and verify something, but I am getting this error.

cy.wait('@request')

will only resolve once an actual request occurs. The error you are receiving is suggesting that the request you are trying to spy on isn't actually getting called. You need to ensure that request actually occurs and can validate this in the runner here in the

#

of times the route was found. Right now it's 0. Additionally, the test runner will output all network calls and provide you information if your intercept matched any request calls.

Yeah the error makes sense but the requests definitely occur when I am not trying to intercept them. I can see them happening in the runner when I comment out that piece of code. Do you think it is a route matching problem? Any other ideas?

It could either be a matching problem or you are defining your intercept too late. The intercept definition needs to always be defined before the request occurs or Cypress won't actually intercept it correctly. I typically define all my intercepts in a beforeEach or at the start of each test so I know there's no conflicts with timing. I would try defining your intercept once outside of the forEach, as this might fix the timing although I don't know exactly what triggers your request. Defining the intercept multiple times is unnecessary anyway. Additionally, I would try replacing the single wildcard char

*

with a double wildcard

**

in your url

I'm not seeing any change when I try those two things. Just in case it helps, this is what my requests look like when I run the tests without the intercept & wait. I am trying to avoid clicking on a bunch of things so just using cy.request(). Do you think that is a problem?

cy.intercept

does not SEE

cy.request

calls https://on.cypress.io/intercept

Oh no 😢 thank you though!

I am trying to delete data from MongoDB by plugin cypress-mongodb but unable to do. Please guide me how can I do delete.

Hello everyone! I'm currently working on a school project, one of the test is to test logout button by cypress, I've search on google and youtube , could not find something to help out.. if someone could help me out with it i will really appreciate it.. "The logout button logs the user out when clicked"

i am trying to read data from Excel

hi there! i am doing kind of listing to study Cypress , so i should find the answer what is going on in those lines of code . I got maybe partially it , but could someone explain every command there

that is what my searches show

The idea of ​​this block of code is to replace the open method before it is called (it's not entirely clear here) .window is a method(cy object command) that gives the object of the page that is currently active. .then - Enables you to work with the subject yielded from the previous command then((window) here we pass the resulting object (as I understand it, you can somehow shorten the name win , is that right?) (window) => { } here we put a new value in our received window object Next, we use the stub command to avoid the following problems. "If an application calls window.open during Cypress test it might lead to two problems: 1)the new URL might point at a different domain, rendering Cypress "blind" and unable to continue the test 2)the new URL might open in the second tab, invisible to Cypress" When we call cy.stub(win, 'open') it replaces win.open method with a Sinon stub function callsFake function dynamically withdraws url which has been placed into original window.open(url, "_blank") window.location = url - redirects us to a new url

also need some help with it .its('0.contentDocument.body')

what does mean 0.contentDocument.body'

what is existing there ?

hi peeps, i was testing cy.intercept() when i console log on the response back to the browser, occasionally the body will have empty body. i want to assert some values in the body but unable to do so. Anyone have guidance on this?

If you're doing

cy.wait()

, then cypress is responding when the endpoint returns something. So it looks like your application is occasionally returning an empty body. That's because the application is logging a 304 (not modified) error

i think im able to simulate something whenever i

npx cypress open

and run the test first time, able to get the body response with 200 Status code but when i re-run the test, this is the moment body responding empty response and with 304 Status Code

What happens when you run it with

npx cypress run

? I'm wondering if it's a shared context thing

let me try

Hi all, In our project we're using snapshot testing. However, some devs are running Windows, some are running OSX and the CI is using linux. Rendering the snapshots could be different on either one of the environments. (fonts, shadow rendering) How do you solve this issue? What we're currently doing is running Docker with Linux locally to match the CI. But it feels a bit odd to be having to use Dockered Linux, a system which our user base don't use.

In other words: How do you get consistent snapshot testing across environments?

i used

cy.task('log', response)

and this is the output