How to use cookieValidatesSecurePrefix method in Cypress

Try declaring the directory path prior to requiring it, using template strings.

var loginPagePath = `${appDir}/src/test/js/cv/pages/LoginPage`;
var LoginPage = require(loginPagePath);

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

Well this seems to work, so it tells me I have some more to learn about .should()

cy.get('.check-box-sub-text').should('not.exist');

Adding cookie whitelist seems to help:

  Cypress.Cookies.defaults({
                whitelist: 'AuthUser'
            })

But as I understand documentaion, Cypress should clear chacke only after all test scenarios in specific test file - not each test scenario?

Accessing new windows via Cypress is intentionally not supported.

However, there are many ways this functionality can be tested in Cypress now. You can split up your tests into separate pieces and still have confidence that your application is covered.

1. Write a test to check that when performing the action in your app, the window.open event is called by using cy.spy() to listen for a window.open event.

cy.visit('http://localhost:3000', {
  onBeforeLoad(win) {
    cy.stub(win, 'open')
  }
})

// Do the action in your app like cy.get('.open-window-btn').click()

cy.window().its('open').should('be.called')

2. In a new test, use cy.visit() to go to the url that would have opened in the new window, fill in the fields and click the buttons like you would in a Cypress test.

cy.visit('http://localhost:3000/new-window')

// Do the actions you want to test in the new window

Fully working test example can be found here.

This worked for me:

cy.get(element).invoke('removeAttr', 'target').click()

Both are utility commands from cypress package, can be performed in the same way (chained off of cy or off another command) and there is no timeout period. But the difference are:

• pause() will stop the test execution to inspect the web application, the DOM, the network, whereas debug() will stop only when the developer tools are open
• pause() does not provide any debug information, whereas debug() give the details in browser console tab
• Using pause() we can find 'next' button option in the test runner, which allow us to execute the code step by step, debug() doesn't have the feature.

Not a cucumber user, but in plain Cypress tests you can only access this by making the callback a function not an arrow function

Given("I check data", function() {
  console.log("this", this.data.user);
});

I think you might have to alias the data as well

before(() => {
  cy.fixture('example')
    .then(function (data) {
      console.log("this", data.user)
    })
    .as('data');
}

Note that Cypress clears aliases in between tests, so you would need to use beforeEach() instead of before().

It looks like the author of cypress-mouse-position never actually published his package to NPM, so I've done it for him.

You should now be able to do npm i -D cypress-mouse-position without encountering any errors, since it is now published on NPM.