How to use sessions.clearCurrentSessionData method in Cypress

Be aware in my js file the following was added automatically;

const { contains } = require("cypress/types/jquery");

deleting this line of code, problem solved

As @Naren says, the space is killing your selector.

You can use an alternate selector (assuming you cannot change the id)

cy.iframe('#podium-modal')
  .find('[id="Mobile Phone"]')
  .type('123456789')

The solution is here: https://github.com/cypress-io/cypress/issues/7402 You have to upgrade cypress to version 4.6.0 and add

{
    "experimentalSourceRewriting": true
}

to cypress.json

You must write a recursive promise function and check by yourself the color text, try the following

function checkColor(selector, color, maxWait, alreadyWaited = 0) {
  const waitTime = 500;
  // cy.get returns a thenebale
  return cy.get(selector).each((item)=> {
    // it checks the text right now, without unnecessary waitings
    if(!item.text() === color) {
      return false;
    }
    return true;
  }).then(result => {
    if(result) {
      // only when the condition passes it returns a resolving promise
      return Promise.resolve(true);
    }
    // waits for a fixed milliseconds amount
    cy.wait(waitTime);
    alreadyWaited++;
    // the promise will be resolved with false if the wait last too much
    if(waitTime * alreadyWaited > maxWait) {
      return Promise.reject(new Error('Awaiting timeout'))
    }
    // returns the same function recursively, the next `.then()` will be the checkColor function itself
    return checkColor(selector, color, maxWait, alreadyWaited);
  });
}

// then, in your test...
cy.addParameter('blue'); //Will send graphQL query to fetch the correct items. 
checkColor('data li', 'blue', 10000).then(result => {
  cy.get('data li').each((item)=> {
    cy.wrap(item).should('have.text', ' blue ');
  });
  // or
  expect(result).to.be(true);
});

I tried to comment a much as possible the code refactoring the code I developed for an accepted similar question.

Let me know if you need some more help ????

UPDATE

We (me and Tommaso) have written a plugin to help you with this kind of checks, its name is cypress-wait-until.

Please thank the Open Source Saturday community for that, we developed it during one of them Saturdays ????

Posting this for people who might run into the same problem in the future.

You can solve this problem by adding "all_frames": true inside content_scripts in the extension manifest.json. This allows the extension to be injected into all frames instead of just the top most frame of a tab

Here's a link for more information on all_frames

You can also add this only when you run cypress by modifying manifest.json before loading the extension into cypress test runner

-Read the manifest from the extension build folder

-Modify content_scripts to include "all_frames": 'true'

-Save the updated version of manifest

I think the problem is, that you want to do conditional testing. Using cy.wait() is bad practice and is even mentioned in the docs itself.

Anti-Pattern

You almost never need to wait for an arbitrary period of time. There are always better ways to express this in Cypress.

You should not execute different actions upon response. In cypress testing it is expected, that you know the result of your action beforehand.

If user enters invalid email, you might expect form submisson to fail and an error to be displayed.

cy.get("#email-input").type('invalid_email.com');
cy.get("#password-input").type(userLoginDetail.password);
cy.get("form").submit();
cy.get(".email-error").should('be.visible');

In this case cypress will check them DOM until it finds the error or hits the defaultCommandTimeout from cypress config.

On the other hand, if you want to check if user is redirected correclty, you can simply check for a div on the success/redirected page.

cy.get("#email-input").type('valid@email.com');
cy.get("#password-input").type(userLoginDetail.password);
cy.get("form").submit();
cy.get(".success-page").should('be.visible');

However, if you still decide to execute an action depending on the servers response, cypress enables you to declaratively cy.wait() for requests and their responses.

cy.server()
cy.route({
  method: 'POST',
  url: '/myApi',
}).as('apiCheck')
cy.visit('/')
cy.wait('@apiCheck').then((xhr) => {
  assert.isNotNull(xhr.response.body.data, 'api call successfull')
})

I was facing the same issue when trying to implement the nodemailer code client side. The reason was because nodemailer doesn't seem to work in the browser (only in node). Moving it serverside (into an express app) solved the issue.

This post regarding the same error (but affecting a different library) also suggests that running the files in the browser is the problem: http://www.ganzhoupress.com/github_/cypress-io/cypress/issues/1981

Hope this helps.

This code is incorrect,

Cypress.on('window:before:load', win => {
  window.foo.abc = true;
});

It should be

Cypress.on('window:before:load', win => {
  win.foo.abc = true;
});

You don't have to use it in before(), but it should be at the top of the spec.

But I suspect it still won't work after correcting, most likely the app resets foo to a new object during loading, i.e during cy.visit()

You can use the 2nd block

cy.visit('...')  // visit before changing

cy.window().then(win => {
  win.foo.abc = true;            // correct the syntax here as well
})

yarn internally uses sh to execute the commands given in the scripts (cmd in case of windows) - Source. This is very similar to what npm does as well.

Here && is handled by a shell, so your command yarn percy:local && yarn start:server percy:exec is run as 2 separate child processes. This means yarn percy:local runs in a process and sets the env variables as desired in its context but the second process which is running yarn start:server percy:exec has no idea about the env variables set by process 1.

Lets see how OS X handles this:

1. With &&

sh -c 'PERCY_TOKEN=asdfasdf; PERCY_BRANCH=local' &&  sh -c 'echo $PERCY_TOKEN'

This prints nothing

2. Without &&

sh -c 'PERCY_TOKEN=asdfasdf; PERCY_BRANCH=local echo $PERCY_TOKEN'

This prints asdfasdf

I think removing the && in the cy:percy:local should fix your issue.

Edit: Solution for your particular situation as discussed in comments

As explained in the 2nd point of this answer: stackoverflow.com/a/37141993/8266093 I would suggest you run this script in the format ENV_KEY1=value1 ENV_KEY2=value2 command which in your case becomes PERCY_TOKEN=$(grep 'PERCY_TOKEN.*' .env | sed 's/.*=//') PERCY_BRANCH=local yarn percy exec cypress run. Along with this, you can add your start-server yarn command as well if running it separately is not a solution for you.