This is not currently supported in Cypress. I built a workaround that might help, though. I set up a simple server that runs in parallel to cypress. The endpoint opens a headless instance of Puppeteer and completes the login flow, responding to the call with all the cookies: const micro = require(“micro”); const puppeteer = … Read more
From https://docs.cypress.io/api/cypress-api/custom-commands.html Put this in your support/commands.js file: Cypress.Commands.add(‘subValues’, (a, b) => { return a – b }); Put this in your support/index.js file, if it isn’t already there (it should be): import “./commands”; Call it in your test like so: describe (‘Calling a function’, function(){ it(‘Call the Subtract function and asert the calculation’, function(){ … Read more
For your usecase of asserting whether an element exists, they are indeed redundant. .contains() yields a DOM element and according to documentation, .should yields the same element it was given as an input. There are some exceptions when .should yields different element (as you can see in the documentation) but in case of using should(‘exist’), … Read more
Cypress .should() wraps chai assertions, so from how to do an “or” in chai should the following html fragment <div id=”1″ class=”class1″></div> <div id=”2″ class=”class2″></div> <div id=”3″ class=”class1 class2″></div> <div id=”4″ class=”class3″></div> can be tested like this it(‘finds either class1 or class2’, () => { cy.get(‘div#1’) .should(‘satisfy’, ($el) => { const classList = Array.from($el[0].classList); return … Read more
To everyone who really need to target class and cannot (Or do not want) use data- attributes for some reasons. Solution is to use standard css selector. cy.get(‘*[class^=”this-is-always-the-same”]’) This will get all elements that has class starting with this-is-always-the-same.
In Cypress version 11.2.0 the Run All button has been reinstated. You need to set experimentalRunAllSpecs to true in cypress.config.js. Please see Configuration – End-to-End Testing
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() })
You can do something like this: // Give an alias to request cy.intercept({ method: ‘GET’, url: ‘/odata/locations/**’, }).as(‘dataGetFirst’); // Visit site cy.visit(‘admin/locations’); // Wait for response.status to be 200 cy.wait(‘@dataGetFirst’).its(‘response.statusCode’).should(‘equal’, 200) // Continue
While this is not the answer you would like to hear, tsconfig.json marks a directory as the root of a typescript project, just like the package.json marks a directory as the root of a node.js project. These files help tools like IDEs to understand your project. In my opinion you should only consider moving tsconfig.json … Read more
@fhilton’s answer used to work, but with newer versions of Cypress, it will cause Chrome to not be able to connect to the test runner and not run any tests. Use this instead: If you or any of your co-workers develop in Windows, run npm i -D cross-env. In package.json add a script to start … Read more