https://cypress.io logo
Join Discord
Powered by
# cy10-feedback
  • f

    full-ram-6858

    06/13/2022, 11:01 PM
    Has anyone else seen the same?
  • s

    swift-angle-95455

    06/14/2022, 1:20 AM
    I'm getting this error. I'm using cypress-realworld-app. Yesterday was running as expected, 2 days ago same.
    • 1
    • 2
  • p

    polite-diamond-19684

    06/14/2022, 1:31 AM
    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)
  • g

    gray-kilobyte-89541

    06/14/2022, 1:39 AM
    I would open an issue with a reproducible example so that bug can be tracked down and fixed
  • p

    polite-diamond-19684

    06/14/2022, 1:40 AM
    Just to show an image. But yeah, I can create an issue. This is a finished successful test that waited on the fetch.
  • g

    gray-kilobyte-89541

    06/14/2022, 2:43 AM
    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
  • t

    thousands-school-59219

    06/14/2022, 9:30 AM
    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?
  • g

    gentle-accountant-4760

    06/14/2022, 9:54 AM
    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
  • a

    able-family-92006

    06/14/2022, 12:39 PM
    Can I collect coverage on Vite app even cypress v10?
  • i

    incalculable-artist-87185

    06/14/2022, 1:17 PM
    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.
  • a

    astonishing-electrician-44897

    06/15/2022, 8:39 AM
    It should be like this
    Copy code
    export default defineConfig({
      e2e: {
        env: {
          FOO: 'BAR'
        },
      },
    });
  • r

    rough-magazine-51515

    06/15/2022, 11:44 AM
    How to run all test in Crypress Application. i can not see where the button is Run all Test
  • h

    hallowed-mouse-50470

    06/15/2022, 5:10 PM
    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
  • d

    damp-kilobyte-10207

    06/15/2022, 6:28 PM
    The Zoom now - is for Automation developers o for Frontend developers?
  • r

    ripe-daybreak-97926

    06/15/2022, 6:32 PM
    Probably both. Frontend developers need to write unit tests.
  • d

    damp-kilobyte-10207

    06/15/2022, 6:34 PM
    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 😦
  • c

    chilly-noon-25793

    06/15/2022, 7:03 PM
    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)?
  • r

    rapid-yak-87393

    06/15/2022, 7:13 PM
    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
  • r

    rapid-yak-87393

    06/15/2022, 7:14 PM
    Component Testing targets front end developers more than automation engineers or QA
  • c

    chilly-noon-25793

    06/15/2022, 7:32 PM
    is there a plan to get code coverage without requiring instrumentation and istanbul?
  • r

    rapid-yak-87393

    06/15/2022, 8:26 PM
    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?
  • c

    chilly-noon-25793

    06/15/2022, 8:31 PM
    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
  • c

    chilly-noon-25793

    06/15/2022, 8:34 PM
    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
  • l

    late-house-1562

    06/15/2022, 8:42 PM
    I'm still a bit of a noob, but more clear and detailed examples are needed for
    setupNodeEvents
  • c

    creamy-noon-1182

    06/16/2022, 7:38 AM
    https://discord.com/channels/755913899261296641/755921564108587038/986621350196178945
  • w

    worried-parrot-50579

    06/16/2022, 8:23 AM
    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?
  • a

    adventurous-postman-3917

    06/16/2022, 9:15 AM
    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.
  • i

    incalculable-artist-87185

    06/16/2022, 3:06 PM
    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:
    Copy code
    "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 🙂 ):
    Copy code
    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.
  • n

    nutritious-honey-65632

    06/16/2022, 6:26 PM
    I run cypress on remote like this
    npx cypress run --browser chrome --env fileConfig=stage
    then inside
    cypress.config.js
    inside
    e2e
    object
    Copy code
    setupNodeEvents(on, config) {
                const file = config.env.fileConfig;
                return getConfigurationByFile(file);
            }
    and function outside of the
    defineConfig
    Copy code
    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
  • l

    late-house-1562

    06/16/2022, 10:10 PM
    I sure am clicking a lot more buttons in order to get test started compared to v9.
1...678...18Latest