nvm I fixed it like this:

ts
    function isClosed () {
        return new Cypress.Promise<boolean>((resolve) => {
                cy.get('.landing-page').first().then(($e) => {
                        if ($e.text().includes('Restaurant Closed')) {
                            console.log("isClosed() <----", true);
                            return resolve(true);
                        } else {
                            return resolve(false);
                        }
                    });
            });
    }

    let isClosedTrue = false;
    specify('Unit test if restaurant is closed', async function() {
        isClosedTrue = await isClosed();
    });

crazy

yeah that's the same solution i used for conditional testing

Headless is fine

Has anyone seen this before? Auto crashing when running cypress open

that is not going to work, and you should not do this. Instead look at the solutions here https://glebbahmutov.com/cypress-examples/recipes/conditional-testing.html

Hey, thanks for the resource! I don't know what you mean by "that's not going to work, because it does work". And the resource you gave me doesn't show any solution to my problem. I cannot see anywhere where to "SKIP" tests "IF" a certain element exists on the page. Handy resource though.

Hey guys, did anyone have ever worked before with synpress (by snyk) or with cypress-metamask (by CraftAcademyLabs) for e2e testing on dapp with metamask wallet?? Or have any ideas on how to create e2e testing on cypress that can work with metamask wallet

any time you use

async

or

await

in Cypress it probably does not do what you think it does. My examples don't include skipping the rest of the test if an element exists, because ... it is weird. But you can probably derive how to do it from the examples

js
cy.get('element selector').should(Cypress._.noop).then($el => {
   if ($el.length) {
      return
    }
    // other test Cypress commands
})

I don't know what "Cypress._noop." is. Couldn't find anything on Google about it either. I could not derive a solution to my question from the examples. In my eyes await just waits for the result of the promise before continuing code execution. Which is what I need to avoid an error. Either "await" or "then". I don't understand why it would be weird? If you could elaborate.

See https://github.com/bahmutov/cypress-examples/commit/18f743bdea31483935f419af896db84db775aab2 and read https://glebbahmutov.com/cypress-examples/9.7.0/recipes/conditional-testing.html and http://on.cypress.io/retry-ability

thanks for the resource, i will take a look when i have the chance.

ts
            let i = 0;
            cy.get('.add-item-to-cart').each((e) => {
                e.trigger('click');
                i++;
            })
            .then(() => {
                cy.get('.cart-size').first().should('have.text', ` ${i} `); // [here].
            });

I changed my code to this.

Maybe write it something like this

js
// the count starts at zero
cy.contains('#count', 0)
// click each button
cy.get('ul button')
  .click({ multiple: true })
  // the displayed count should equal the number of buttons
  .its('length')
  .then((n) => {
    cy.contains('#count', n)
  })

See https://github.com/bahmutov/cypress-examples/commit/4eeb2af1f9ac56e14e9c70416d1c3a3b0cf94e00

I will take a look, thanks for the example!!

I had a similar issue on my end. This was solved by bypassing a network protection setting in Sophos (antivirus we use, company policy).

Hi, is there anyone can help me? I have a test case for clicking banners on the website, but I have to scroll first so that the elements are loaded and clickable. I'm having trouble getting my elements to be found by cypress. Anyone have a solution?

Hey people. I have an issue with running cypress in a docker container. It passes tests in --browser firefox --headless but fails in --browser chrome --headless. Anything comes to mind straightaway?

I serve app files in nginx that cypress then navigate to

Are the elements in the dom?

What are you trying

Becuase this sounds like one of the simpler cases in Cypress -- call cy.visit to load the page, cy.get().scrollIntoView(), and then cy.click()

Hi there can anyone maybe assist me i have an issue where i am getting this error 429 - too many requests

Hi, your server is protecting itself from repetitive requests in a short timelapse ( useful to prevent DDOS attacks). Either you need to update such a setting for a stage environment if you are making a lot of requests through repetitive testing, either you need to test such error as it's the success of a feature.

im unsure inside github actions yml if i should use github action or docker image to run the tests, because they seem to do same thing? so im not sure based on which criteria i should pick one or another?

Hi When I run a cypress test an error message is shown from the website but I can do the test manually and there are no error messages only when I run the same test via cypress its showing the error message is there a solution

I've try using scrollIntoView() but Cypress keep saying that my elements never found.. But if I try to manually scrolling my browser (when the test running), it will success find my element

try

scrollIntoView({force: true})

?

I tried to try this and still my element is not found by cypress. maybe because it hasn't been loaded yet. because I have to manually scroll down first..

you could try this if your elements are lazy loaded (found some time ago in percy documentation):

let scrollToBottom = require("scroll-to-bottomjs");

describe("Lazy loading example", () => {
  it("captures lazy loading images", () => {
    cy.visit("https://sdk-test.percy.dev/lazy-loading");
    cy.window().then(cyWindow => scrollToBottom({ remoteWindow: cyWindow }));
    cy.percySnapshot("Lazy loading images");
  });
});

Any promo code to Cypress network testing exercise