This does exactly what I needed of catching any error in the console and do an assertion of the logs count. Just add the following in cypress/support/index.js Cypress.on(‘window:before:load’, (win) => { cy.spy(win.console, ‘error’); cy.spy(win.console, ‘warn’); }); afterEach(() => { cy.window().then((win) => { expect(win.console.error).to.have.callCount(0); expect(win.console.warn).to.have.callCount(0); }); });
As of 4.0.0, Cypress offers matchCase option with contains… cy.get(‘div’).contains(‘capital sentence’, { matchCase: false })
You can wait for the element to be visible like so: // Give this element 10 seconds to appear cy.get(‘[data-test=submitIsVisible]’, { timeout: 10000 }).should(‘be.visible’); According to Cypress’s Documentation: DOM based commands will automatically retry and wait for their corresponding elements to exist before failing. Cypress offers you many robust ways to query the DOM, all … Read more
Short answer: You can write your login command in a before hook within the supportFile (the file that is loaded automatically before your other spec files). This before hook will run before any of the code in your other test files. Recommendations: That being said, this approach leaves little flexibility for variation in your individual … Read more