Updated for Cypress v7.0.0 Released 04/05/2021 The change-log shows from this release the intercepts are now called in reverse order Response handlers (supplied via event handlers or via req.continue(cb)) supplied to cy.intercept() will be called in reverse order until res.send is called or until there are no more response handlers. Also illustrated in this diagram … Read more
To force an arbitrary loop, I create an array with the indices I want, and then call cy.wrap var genArr = Array.from({length:15},(v,k)=>k+1) cy.wrap(genArr).each((index) => { cy.get(“#button-” + index).click() })
Dispatching MouseEvents seems to be the only way to test Angular Material drag and drop. You should also be aware of the following issue, which tests in Protractor but also applies to this Cypress test CDK DragDrop Regression between 7.0.0-beta.2 and 7.0.0-rc.2: Protractor tests stopped working #13642, It seems that (for want of a better … Read more
The short answer is, the Stripe iframes take time to load and display the fields you need to access, so you need to add a retry. Usually you use .should() assertions to retry until something you want is present in the DOM. Unfortunately, with an <iframe> inside the page, you can’t use .should() because it … Read more
The soft assertion concept is pretty cool, and you can add it with minimal implementation to Cypress const jsonAssertion = require(“soft-assert”) it(‘asserts several times and only fails at the end’, () => { jsonAssertion.softAssert(10, 12, “expected actual mismatch”); // some more assertions, not causing a failure jsonAssertion.softAssertAll(); // Now fail the test if above fails … Read more
Material Design Select and Cypress This is the same basic problem as Access element whose parent is hidden – cypress.io, except this question is angularjs + md-select and that question was angular + mdc-select. Nevertheless, the two versions of material design select use the same trick of making the parent control invisible (by setting width … Read more
Your problem stems from the fact that cypress commands are not promises, although behaving like promises. I can think of two options: Try to refactor your test code to not use async/await, as these commands don’t behave as expected when running your code on cypress (check this bug). Cypress already has a whole way of … Read more
Docker exit code 137 may imply Docker doesn’t have enough RAM to finish the work. Unfortunately Docker consumes a lot of RAM. Go to Docker Desktop app > Preferences > Resources > Advanced and increase the MEMORY – best to double it.
The code below should do what you’re trying to achieve. There is also an entire recipe with suggestions on how to test links that open in new tabs. it(‘Advertise link should refer to Contact page’, () => { cy.get(‘div.footer-nav > ul > li:nth-child(2) > a’) .should(‘have.attr’, ‘href’).and(‘include’, ‘contact’) .then((href) => { cy.visit(href) }) }) I … Read more
As of Cypress 3.0.0, you can use cy.task() to access node directly and output to the node console. From the docs: // in test cy.task(‘log’, ‘This will be output to the terminal’) // in plugins file on(‘task’, { log (message) { console.log(message) return null } }) See here for more info. I don’t know of … Read more