@User ^^

sorry @User I missed your message, I'm a NZ time zone

I'm unable to run cypress after a fresh installation today

rosetta error attachment of code signature

Hi guys! My website requires a login, that is on an other domain. How can i create tests without the annoying 2 super domains error? Is there a trick like using tasks (save and load data across tests)? I can't be the only one that has this problem.. How do other people surpass this issue?

Hello, I found out that cypress docker image is not publish in docker repo (https://hub.docker.com/r/cypress/included/tags) in lastest version 9.5.1? Is that intentional? (only 9.5.0 exists)

There was a delay in publishing, but it should be available now. Can you confirm 9.5.1 is available to you?

Hello, Can someone here help me? Scrolling horizontally to find an element is failing Test code to reproduce it('should scroll right & click on march column', () => { cy.visit('https://www.ag-grid.com/example.php%27); cy.get('div.ag-center-cols-viewport div[row-id="0"] div[col-id="mar"]') .scrollIntoView() .click(); }); I have also tried scrollTo('right'), but in my case the element's position is not the extreme right.

thank you very much, its published now.🙏

I want to do a global retry of 1 in CI but 0 locally. We use cypress.run() to kick off our tests in CI. It seems that retries is not an option in cypress.run (https://docs.cypress.io/guides/guides/module-api#Options). Any ideas on how to achieve my goal? Thanks.

Hello people: Bug or feature?

/usr/local/bin/npx cypress cache list
┌─────────┬──────────────┐
│ version │ last used    │
├─────────┼──────────────┤
│ 3.8.3   │ a minute ago │
├─────────┼──────────────┤
│ 9.4.1   │ a minute ago │
├─────────┼──────────────┤
│ 9.5.1   │ 4 days ago   │
└─────────┴──────────────┘
build app command "npm run build"

Hi, was wondering if using case switches be good or bad practice rather than using if else conditionals in Cypress ?

Not sure. Good question but I think in general, even if using switch statements fall under "conditional testing" and should be avoided. The bottom line is that the test, or tests, are then non-deterministic and that's a "no no".

lets say if I had conditional testing done because of different settings would that still be bad practice?

Hmn, good point. That might be more acceptable. How many different combinations of settings do you have? So much so that you can't just have a different test for each setting?

About 5 settings, the cases are related to what setting is clicked under for each page but they all have the same fields to be adjusted on

So even if you only had 1 test to accommodate those 5 different options...you would still know and be able to control which path the test execution takes right?

yeah it would be under a specific tag for a specific page that is passed onto a function beforehand

I'd be inclined to go the 1 test route vs. 5 so as to avoid the suite of tests blowing up in volume and of course possible needed maintenance in the future. Bit of a judgement call.

someithng liek this

Hi all, I am currently in the process of switching my javascript tests to typescript. After I switch one of my testsfiles to .ts and tried to run it I got the following error:

javascript 
Error: Webpack Compilation Error
./tests/e2e/specs/requestDetails/application/applicationE2E.ts 300:101
Module parse failed: Unexpected token (300:101)
File was processed with these loaders:
 * ../../../Library/Caches/Cypress/9.5.0/Cypress.app/Contents/Resources/app/packages/server/node_modules/ts-loader/index.js
You may need an additional loader to handle the result of these loaders.
|                 getCopyBtn("connectee", "assetAddress").click();
|                 cy.get("[data-cy='record-section-assetAddress-street-value']").then((street) => {
>                     cy.get(`[data-cy="record-card-connectee"]`).should("contain.text", street.val() ?? "-");
|                 });
|                 cy.get("[data-cy='discard-request-changes-and-cancel-edit-mode']").click();

looks to me that cypress is not able to process the Nullish coalescing operator (??). The same error appears with the Optional chaining (?.) operator. Do you know what i can do so that cypress likes my operators again? Here my

tsconfig.json

json 
{
  "compilerOptions": {
    "noEmit": true,
    "types": ["cypress", "cypress-file-upload", "node"]
  },
  "include": ["./**/*.ts", "support/commands.js"],
}

Thanks in advance 😁

All right, this here brought me on the right track: https://github.com/TypeStrong/ts-loader/issues/1061 here the tsconfig with which it works: the

compilerOptions

need to have

target

set to

es2019

Hi, first off, it is nice to see that a place like this exists. Cypress truly does provide a top-notch developer experience 👍

Second, I am in the process of upgrading a few tests to run with a newer version of cypress (8.1.0) and I running into something quite curious. It seem that cypress has trouble recognizing that a spec contains any test at all if it contains a template literal with multiple insertions (or whatever they are called. In other words, when my tests contain this:

cy.location('search')
  .should('eq', `?${filters.first.key}=${filters.first.value}&${filters.second.key}=${filters.second.value}`)

It gives me the message "No tests found" But when I change it to:

cy.location('search')
  .should('eq', ' ?' + filters.first.key + '=' + filters.first.value + '&' + filters.second.key + '=' + filters.second.value)

All the tests are recognised and run! Side note, this does work:

cy.location('search')
   .should('eq', `?${filters.first.key}=R007`)

Hey guys

how do I avoid the cypress proxy?

nybody running cypress with Google Cloud Firestore recently? Inside cypress adding a document takes as much as 45 seconds for xhr response. Outside of cypress (local serve of app) it takes about 1.5 seconds. Does cypress do anything internally that could be causing xhr slowness?

hi, I just want to ask, how can I setup my flaky management in cypress dashboard? We have now a premium account and even after I input the retries command on cypress.json, the flaky management report is not appearing. hoping that someone can help me with this. thank you