How to use sessions.setStorage method in Cypress

This is a known issue after Chrome 67 enabled by default the site isolation security feature, and it gets reflected in any frameworks that use Chromium releases that include it (e.g. Electron 5+)

http://www.chromium.org/Home/chromium-security/site-isolation

When debugging with --disable-web-security, it may also be necessary to disable Site Isolation (using --disable-features=IsolateOrigins,site-per-process) to access cross-origin frames.

Here are some open issues regarding it

https://github.com/electron/electron/issues/18214
https://github.com/cypress-io/cypress/issues/1951

In Electron 5+, until this is solved you can add this line before app 'ready' event

app.commandLine.appendSwitch('disable-site-isolation-trials');

It looks like you are modifying a test file within the Cypress installation. This is probably not what you meant to do.

There are two important components to Cypress:

1. The Cypress package installation. In your case this is installed at c:\node_modules\.bin\cypress
2. The Project under test also has some Cypress related files, including cypress.json in the top level directory of the project, and the test files located in the cypress folder within the project directory (unless you have told Cypress to use a different directory).

When you run Cypress tests on a project, the test files which are watched are those that are located within the project directory - not those within the Cypress installation itself.

When you run cypress open then you can manually select the directory of the project that you want to test, say it is C:\MY_PROJECT. If there is no cypress.json file and no tests found, Cypress will automatically create a cypress.json file and a cypress directory within C:\MY_PROJECT. Inside the C:\MY_PROJECT\cypress\integration\ directory will be some example tests. When you edit tests in this directory with watchForFileChanges=true and manually choosing C:\MY_PROJECT to test, they will automatically rerun when saved.

I have also tested running and modifying the tests in the example directory within the Cypress package within the node_modules directory. I can confirm that when files within that directory are edited, the tests do not rerun. However, it is a mistake to edit those files when you are trying to test one of your own projects.

HTH

You can use day.js to get the current date and format it accordingly.

const dayjs = require('dayjs')

//In test
cy.log(dayjs().format('DD/MM/YYYY'))  //Prints todays date 30/09/2021
cy.get('textfield').type(dayjs().format('DD/MM/YYYY')) //input today's date in DD/MM/YYYY format

I don't think aliases are required. Here is my solution that I tested locally. I kept most of the code in Alapan Das' answer so it's easier to compare. To me, it seems more concise and easier to read without aliases.

describe('Store and compare a value', () => {
    it('store and compare', () => {  
        cy.login()
        cy.visit('url2')
        cy.get('.total-count-results').invoke('text')
            .then((previousText) => {
                cy.get('.medium.col100 > .filterwrapper > input').type('Test Dummy',{force: true})
                cy.get('.medium.col100 > .filterwrapper > input').type('{enter}')
                cy.get('.total-count-results').invoke('text').should("eq", previousText)
            })
    })
})

All the code and referenced modules in index.js are loaded before your test file. So you need to refer(require) commands.js in your index.js file. You can however import commands.js module directly in your test file but then you need to include it every test file. Recommended approach is to include it in index.js file and you are not worried about explicitly refer in your test files.

You can read the csv file from spec file using:

cy.readFile('file.csv')
  .then((data) => {
     cy.task('csvToJson', data).then((data) => {
            //process data
        })
   })

After that you create a task in plugins/index.js

csvToJson (data) {
  var lines=data.split("\n");
  var result = [];
  var headers=lines[0].split(",");
  for(var i=1;i<lines.length;i++){

      var obj = {};
      var currentline=lines[i].split(",");

      for(var j=0;j<headers.length;j++){
          obj[headers[j]] = currentline[j];
      }
      result.push(obj);
  }
  // console.log(result)
  return result
}

This will will do the job

@JeremyKahan is correct, it's like mixing synchronous and asynchronous code. The synchronous code always executes first.

Basically, you can see it by adding a couple of console.log()

function getProfilePresentOrNot(profileName) {
  var flag = 0;
  cy.get("li>div>div>span").each(($el, index, $list) => {
    if ($el.text().includes(profileName)) {
      console.log('Setting flag')
      flag = 1;
    }
  });
  console.log('Returning flag')
  return flag;
}

This will print in the devtools

Returning flag
Setting flag                // because cy.get(...).each(...) ran later

You could use a custom command

Cypress.Commands.add('getProfilePresentOrNot', (profileName) => {
  cy.get("li>div>div>span")
    .invoke('text')                                  // all text from all spans
    .then(allText => allText.includes(profileName))  // returns the result of .includes(...)
})

which must be used like this

cy.getProfilePresentOrNot('someprofilename')
  .then(isPresent => {  // true or false
    if (isPresent) {
      ...
    }
  })

or if you are absolutely sure that all li>div>div>span are present in the page, you can still use a function but switch to synchronous Cypress code (i.e jQuery).

function getProfilePresentOrNot(profileName) {
  const allText = Cypress.$("li>div>div>span").text()
  return allText.includes(profileName);
}

which can be called like this

const isPresent = getProfilePresentOrNot('someprofilename')

The custom command is safest because on a production web page there are lots of things that can fail your test because the element can't be found immediately, and Cypress asynchronous commands have built-in mechanisms to avoid the problems.

You may have noticed the polite discussion about dismissing the popups, is it necessary or not.

I believe not, and to rely on dismissing the popups will give a flaky test.

I also think the issue is as @DizzyAl says, the event handler on the dropdown button is not attached until late in the page load.

This is what I tried, using retries to give a bit more time for page loading.

Cypress.on('uncaught:exception', () => false)

before(() => {
  cy.visit('http://mercadolibre.com.ar')
  cy.get(".nav-search-input").type("scanner bluetooth para auto{enter}");
  cy.get('.ui-search-result__wrapper')  // instead of cy.wait(3000), wait for the list
})

it('gets the dropdown menu on 1st retry', {retries: 2}, () => {

  // Don't dismiss the popups

  cy.get('button.andes-dropdown__trigger').click()
  cy.contains('a.andes-list__item', 'Menor precio').click()

  // page reload happens
  cy.contains('.ui-search-result__wrapper:nth-child(1)', '$490', {timeout:20000})
});

You can use Object.values in js to retrieve values from your object

Let's say you need to extract the value of the 3rd column, so your code will look like,

cy.task('DBQuery', query).then(function (recordset) {
    var rec = recordset
    const results = Object.values(rec[0])
    // results[index of the column] will output the results
    cy.log(results[3])
})

We can do a small modification to make your task easier,

cy.task('DBQuery', query).then(function (recordset) {
    var rec = recordset
    const Values = Object.values(rec[0]);
    const keys = Object.keys(rec[0]);
    let result = {};
    let index = 0;
    keys.forEach(key => {
        result[keys[index]] = Values[index];
        i++
    })
     //result.firstName will give you your results
     cy.log(result.firstName);
})

In this way, we are generating key-value pairs having the key as the column name. So you can use the column name to find the value.

Hope this helps.

cheers.