How to use convertPathToPosix method in Cypress

Friends

Firstly, Thanks for all your time & suggestions.

I have found the work around to trigger the mouseover event and show the bootstrap submenu. without using the { force: true }.

Solution that I implemented. Appreciated if anyone finds different and better solution. Please do share.

Cypress.$($elem[0]).siblings("ul").show();

Using this I have manually makes the ul to show first and then execute the click event of the submenu. For this I have tried

Cypress.$($elem[0]).hover(false, false);
Cypress.$($elem[0]).mouseover();
Cypress.$($elem[0]).trigger("hover");
Cypress.$($elem[0]).trigger("mouseover");

but above commands didn't work. So I move to manually trigger the hide/show event of jquery.

Preserve cookies between tests with Cypress.preserveOnce(), or in beforeEach() preserves for all tests.

beforeEach(() => {
  Cypress.Cookies.preserveOnce('test_email')
})

it('set cookie', async () => {
  cy.setCookie('test_email', 'fake@email.com')
})

it('once', async () => {
  const email = await cy.getCookie('test_email')
  expect(email).to.have.property('value', 'fake@email.com')  // passes
})

it('twice', async () => {
  const email = await cy.getCookie('test_email')
  expect(email).to.have.property('value', 'fake@email.com')  // passes
})

it('thrice', async () => {
  const email = await cy.getCookie('test_email')
  expect(email).to.have.property('value', 'fake@email.com')  // passes
})

You should stick with the documented way of using getCookie.

If I run

const email = await cy.getCookie(...)

after a cy.visit(), I get undefined.

If I use

cy.getCookie(...).then(...) 

on the next line it gets the value.

Since Cypress has not documented the await syntax anywhere, you are likely to get some flaky results.

Standard pattern is:

it('once', () => {
  cy.getCookie('test_email').then(email => {
    expect(email).to.have.property('value', 'fake@email.com')  // passes
  })
})

If you run tests in CI they may be run parallel, so better to setCookie in before() or beforeEach().

before(() => {
  cy.setCookie('test_email', 'fake@email.com')
})

beforeEach(() => {
  Cypress.Cookies.preserveOnce('test_email')
})

it('uses cookie once', () => {
  ...
})

it('uses cookie twice', () => {
  ...
})

it('uses cookie thrice', () => {
  ...
})

As the message says, .select() is the command to use

cy.get('[name^=shopveg]').select('Bananas')

That's because <select> behavior is implemented by a web component (see slot tag), not javascript, so there's no click handler available.

To expand on @JosePita's idea, you can set up glob patterns in scripts (package.json) and by-pass the multitude config files he was concerned about.

For example, these work on my system,

"scripts": {
  "cy:open": "cypress open",                              // all files
  "cy:user": "cypress open -c testFiles=user/**/*",       // just the user folder
  "cy:error": "cypress open -c testFiles=**/*error*.js",  // files with keyword 'error'

There's a search bar at the top of the Cypress runner, where the tests are listed, but search is all it does.

Pressing the Run all specs button runs the full set regardless of search results.

If you want to run a subset, specify the testFiles config option on the command line.

Cross domain is not supported in Cypress.

Example: step 1: You navigate to google step 2: Search for Gmail step 3: clicked on gmail link

You are switching from Google.com to gmail.com - cypress doesn't support this.

Workaround 1: You can remove set href attribute value to blank as below:

target="_blank" so that it will open in same page.

Workaround 2:

put step 1 and step 2 in one test iteration

and put step 3 in another iteration

Instead of putting the loop inside the test, you could put it in the outer space as following

var i = 0;
for (i = 0; i < 3 ; i++) {     
  describe('Verify "Login" is visible. Test: '+i, function() {
    it('finds the Login link in the header', function() {

      //Place code inside the loop that you want to repeat

    })
  })
}

The Result will be the following:

• Verify "Login" is visible. Test: 0
• finds the Login link in the header
• Verify "Login" is visible. Test: 1
• finds the Login link in the header
• Verify "Login" is visible. Test: 2
• finds the Login link in the header

Attribute selectors require square brackets, and they don't "have.text" instead you must invoke the .attr() method to get the attribute value.

cy.get('#container [data-test]').eq(0)
  .invoke('attr', 'data-test').should('eq', 'diamond-blade')

cy.get('#container [data-test]').eq(1)
  .invoke('attr', 'data-test').should('eq', 'fire-sword')

cy.get('#container [data-test]').eq(2)
  .invoke('attr', 'data-test').should('eq', 'emerald-stone')

cy.get('#container [data-test]').eq(3)
  .invoke('attr', 'data-test').should('eq', 'black-leather')

Like this for example:

it('Some test', () => {
    cy.intercept('/').as('myRequest');
    cy.visit('www.example.com');
    cy.wait('@myRequest').then((interception) => {
        cy.log(interception.response.body);
    });
});

To listen for only ads requests use cy.intercept('/ads'). Remember to put intercept before you open the page.

Reference: https://docs.cypress.io/api/commands/intercept

2022 here and tested with cypress version: "6.x.x" until "10.x.x"

You could use { force: true } like:

cy.get("YOUR_SELECTOR").click({ force: true });

but this might not solve it ! The problem might be more complex, that's why check below

My solution:

cy.get("YOUR_SELECTOR").trigger("click");

Explanation:

In my case, I needed to watch a bit deeper what's going on. I started by pin the click action like this:

Then watch the console, and you should see something like:

Now click on line Mouse Events, it should display a table:

So basically, when Cypress executes the click function, it triggers all those events but somehow my component behave the way that it is detached the moment where click event is triggered.

So I just simplified the click by doing:

cy.get("YOUR_SELECTOR").trigger("click");

And it worked ????

Hope this will fix your issue or at least help you debug and understand what's wrong.