that's it right, it's very hard to diagnose those plugin and task failures you can configure cypress tsconfig independent of the top level tsconfig that repo has an example, but here are CRA and vite templates with TS, prettier, eslint, cypress, GHA etc etc. https://github.com/muratkeremozcan?tab=repositories&q=template&type=&language=&sort=

you might need to turn off that experimental flag @few-farmer-48800 you ran into it , what was it? without it, you might need to enhance some of that test code to start using cy.session, but doesn't sound like you want exactly that with the tests

Thanks @magnificent-finland-58048 , Which experimental flag are you referring to?

That's it

If you're doing that you need to add in testIsolation: false to your config

Thanks @few-farmer-48800 I've already tried that prior to posting the question and it doesn't work either. Sorry for not putting it before

I've posted my question here https://github.com/cypress-io/cypress/discussions/25437 FYI

that s it right it s very hard to

hmm , difficult to say anything without looking at reproducible code, but it might be forcing to do things the cy.session way now

take a look at https://github.com/muratkeremozcan/auth0-cypress/blob/master/cypress/support/commands.js

thank you @magnificent-finland-58048 will do 🙂

I guess I did mis-read a little bit

You log in and logout after every test?

If so, maybe that's the difference. We log in once and maintain that state

How do test update functionality on cypress?

it.only('sends ticket to completed by pressing title',()=>{
      cy.intercept({
        method: 'GET',
        url: 'some secret url lol'
      },{
        fixture: 'activeTickets.json'
      });
      cy.get('[data-test="activeTicketsCollection"]').should('be.visible');
      cy.contains('ChiChi K.').should('be.visible').click();

      cy.intercept({
        method: 'PATCH',
      }, {fixture: 'activeToComplete.json'}).as('updatedList');
      cy.wait('@updatedList').then(({response}) => {
        expect(response.body).to.have.length(2);
      });

im using fixtures to bring in an "active list". upon clicking it listen for the patch request . then should i bring in a seperate fixture for 'update' ? And how do i get the new fixture to show on my ui? or am I doing this wrong all together?

You are doing it wrong. https://glebbahmutov.com/blog/cypress-intercept-problems/#the-intercept-was-registered-too-late

i am getting memory issue how to fix that issue

Create a mock server I need guidance on an assessment I need to do (screenshot attached). As I understand, I need to create a mock server and then test it. Checking on Internet how to create the mock server, I found this: https://www.mocks-server.org/docs/integrations/cypress/ , but being honest I don't understand how to use it. I was trying to figure out how to configure it and use it, but no success. Also I was searching for samples on Internet, but the only sample is the existing documentation of the library. Documentation is not clear for me. I haven't done mock servers in the past, and I'm totally confused with this. Is there any other way to do this? Can someone help/guide me? Thanks in advance for your help, guys.

hi I wrote loop condition while I am running test cases i getting out of memory issue

Hello I'm trying to migrate from cypress v8.3 to cypress v10+, the migration tool didn't work at first so I had start from scratch and update it manually so I might have missed something, here's my error, anyone encountered this before? Thanks in advance!

removing defineConfig wrapper did the work, although it will remove cypress code completion or so it says here https://docs.cypress.io/guides/references/configuration#Intelligent-Code-Completion

Hi, our pipeline has started to fail giving this error message (it was working fine before with the same config):

The run you are attempting to access is already complete and will not accept new groups.
The existing run is: https://cloud.cypress.io/projects/naz8rj/runs
When a run finishes all of its groups, it waits for a configurable set of time before finally completing. You must add more groups during that time period.
The --tag flag you passed was: development
The --group flag you passed was: firefox
The --parallel flag you passed was: true
https://on.cypress.io/already-complete

not sure what it means by

you must add more groups during that time period

groups are defined this way in the

package.json

"cy:run:chrome": "cypress run --browser chrome --group chrome",
"cy:run:firefox": "cypress run --browser firefox --group firefox",

Our current Run completion delay is set to 60s, but not sure if it would help changing it And this is the config for the failing gitlab-ci job:

e2e_development_firefox:
  image: cypress/browsers:node16.16.0-chrome107-ff107-edge
  stage: e2e
  parallel: 2
  needs: [deploy]
  only:
    - merge_requests
  script:
    - $(npm bin)/cypress cache path
    - $(npm bin)/cypress cache list
    - $(npm bin)/cypress verify
    - npm run cy:run:firefox -- --tag development --key <key> --record --parallel --config baseUrl=${DYNAMIC_ENVIRONMENT_URL}

so in the end the solution was to use the group option inside the gitlab ci stages instead of the package.json scripts

in my package.json

"cypress-cucumber-preprocessor": {
    "nonGlobalStepDefinitions": true,
    "stepDefinitions": "src/integration/**/*.{js,ts}"
  }

is there a way to isolate step definitions, for example the feature file in

integration/feature1.feature

uses the step definition in:

integration/feature1/testFile.ts

Hi all! This is a silly one, I couldn't find about though: setting the corresponding value to DEBUG variable as an admin in macOS does not seem have any effect in the subsequent headless run of my tests (no extra messages are printed). I'm on Cypress 9.5.0, BTW. Thanks!

Question for you, does Cypress clear cookies between each it{} block?

Solved the basicAuth issue after 2 weeks of brain pain 😄 maybe someone will find this interesting: turns out i needed to add 'www.' to my baseUrl. The difference in basic auth on a domain with 'www.' and without it is likely due to the way the website's server is configured. The server administrator may have set up different authentication settings for the 'www' version of the domain and the non-www version.

Hey there! I added Cypress to my docker-compose. I've rebuilt my container, but I seem to running into an issue where I can never get the image to run. There are no logs either