Has anyone else seen the same?

I'm getting this error. I'm using cypress-realworld-app. Yesterday was running as expected, 2 days ago same.

I'm pretty sure my situation is a bug. Although I don't know the root cause. I do use msw during development but turn it off during testing. But I'm suspicious that it could cause this issue. When the fetch is logged, it spins indefinitely, even though the interceptor worked and the wait worked. And then the next test that uses an interceptor fails. (Just component testing)

I would open an issue with a reproducible example so that bug can be tracked down and fixed

Just to show an image. But yeah, I can create an issue. This is a finished successful test that waited on the fetch.

I think that is just UI issue. The test is done, and that fetch is ongoing, so the UI shows it as spinning at the moment of the test

had a really hard time migrating a vite-vue-typescript project from 9.6 to 10. Several errors and problems, took me more then half a day. now it mostly works but i have the strange situation that i can only run cypress for this project from commandline but if i try to open the project in the desktop app i get only an endless spinner, no errors in debugger. cleand up app and appData serveral times (i am on windows) . Feel quite helpless what to do next. And as i sayd: triggered by npm script it runs. Any idea how to find the problem?

It looks like the automatic migration did not work for me when it should have added the setupNodeEvents for

./cypress/plugins/index.ts

instead it added empty row

Can I collect coverage on Vite app even cypress v10?

HI all, First time here, has anyone tried the** cypress.env()** to set environment variables? **module.exports = defineConfig({ env: { FOO: 'BAR', }, })** But then if I do Cypress.env('FOO'), then I get an undifined back.

It should be like this

export default defineConfig({
  e2e: {
    env: {
      FOO: 'BAR'
    },
  },
});

How to run all test in Crypress Application. i can not see where the button is Run all Test

Just click on the test it will run the specified test in Cypress runner Else You can also run an entire suite from command with specified browser

The Zoom now - is for Automation developers o for Frontend developers?

Probably both. Frontend developers need to write unit tests.

Thanks, because I am not a Frontend developer - I was wondering if maybe I shouldn't be here - the React.js is not familiar to me 😦

would like to get answer to how do we get component test code coverage? also how do we get overall code coverage instrument with an external plugin (e.g. istanbul)?

Hi @chilly-noon-25793 , heres our doc on code coverage: https://docs.cypress.io/guides/tooling/code-coverage. It needs to be updated slightly for some CT specific things but should get you up and running. Heres a sample create-react-app thats using both e2e and CT tests with code coverage: https://github.com/elylucas/cypress-cra-code-coverage-example

Component Testing targets front end developers more than automation engineers or QA

is there a plan to get code coverage without requiring instrumentation and istanbul?

Theres nothing on our official roadmap for that yet, but we have discussed internally what it might look like if we had instrumentation out of the box with Cypress. Would you find value in that?

thanks. that would be enormous save for us in maintenance of the instrumentation required packages. currently we are missing coverage due to some updates in the packages that broke the functionality. it would be awesome if cypress would provide coverage out of the box. code cove brings huge value prop for business and helps provide them visibility on the current test state

also how awesome it would be see the code coverage numbers on cypress dashboard. even a visualization of numbers going up down with each run

I'm still a bit of a noob, but more clear and detailed examples are needed for

setupNodeEvents

Hey guys, I only automate E2E flows. Is it still worth upgrading to v10 or can I stay with the current version to save all the migration changes to support/config files?

Hey @worried-parrot-50579, you can continue with 9.x but in my opinion, as it is a big update with a lot of changes from cypress, better to update your projects asap. The later, the harder.

Thanks! Though still cannot get it to work. I run my E2E's using a configfile depending on the environment (so different config for TST, ACC, etc.). So the package.json says:

"scripts": {
        "cypress:opentst": "cypress open --env configFile=testEnvConfig",
        "cypress:openacc": "cypress open --env configFile=accEnvConfig"
}

So now I have a Typescript file called 'testEnvConfig' like this (thanks for that 🙂 ):

export default defineConfig({
  e2e: {
    env: {
      FOO: 'BAR'
    },
  },
});

Cypress picks up the env configuration if I put it in cypress.config.ts, but for some reason it does not pick it up from my 'testEnvConfig' file if I specify the fiel in the CLI.This used to work in Cypress 9 (when my config file was still json). So I am puzzled why it no longer picks it up now. Name of the file remains the same, it is just TS instead of JSON.

I run cypress on remote like this

npx cypress run --browser chrome --env fileConfig=stage

then inside

cypress.config.js

inside

e2e

object

setupNodeEvents(on, config) {
            const file = config.env.fileConfig;
            return getConfigurationByFile(file);
        }

and function outside of the

defineConfig

const fs = require('fs-extra');
const path = require('path');

function getConfigurationByFile(file) {
    const pathToConfigFile = path.resolve('./cypress/', 'config', `${file}.json`)

    return fs.readJson(pathToConfigFile);
}

my actual config file live in

cypress/config/stage.json

I sure am clicking a lot more buttons in order to get test started compared to v9.