New answers tagged

2

The answer is, it depends. It would be helpful to know more information on the makeup of your team/organization. How many people do dev work, QA work, DevOps work? How many team members and the setup of the team can make a difference to solutions. Option 1: You can keep your e2e and performance tests in the same repository as your application if you're the ...


0

First off, Cypress is not the only tool that fits all problems. If it doesn't work for you, perhaps it's time to try a different tool. You don't need to use Cypress just because it seems pupular. Back to the question. I'd try two things: 1/ cross-domain Browsers do not allow JS from one domain to access elements from another domain, so if your iframe is a ...


1

I might be late to answer. If you are looking specifically for coverage while using Cypress for E2E, you can check this doc: https://docs.cypress.io/guides/tooling/code-coverage.html#Introduction Here it is shown that we can measure code coverage using additional plugins though this coverage is just an indicator of what all lines of code are not at all ...


1

Aliases in Cypress are removed between tests, that's why your response alias is not preserved. A discussion around this topic could be found e.g. here. What works is this code: const { expect } = require("chai") describe('When requesting the resource', () => { let response; before(() => { cy.request('http://startpage.com/')....


1

You can set the viewport’s width and height globally by defining viewportWidth and viewportHeight or alternative function .viewport which supports below strings: Example: Pre-requisite: -Install NodeJS version 8 or above along with JAVA in your laptop Clone Repository: https://github.com/narayananpalani/cypress-test-techniques Install using commands below:...


Top 50 recent answers are included