There is no option to do it with Cypress 10

See Gleb's workaround: https://glebbahmutov.com/blog/run-all-specs-cypress-v10/

Hellooo 👋 I've got an issue with

before:spec

. Apologies if this isn't the right place to raise this - feel free to send me to the right place! Thought I'd post here before raising an issue on github, I searched the issues and couldn't find anything related

before:spec

is triggered

when running cypress via cypress open, the event will fire when the browser launches

This means that the values within

spec

are no longer filled - as before Cypress 10, the browser was launched after selecting a spec file. Is this a known issue / is there a workaround ?

Hellooo 👋

Hi , I'm resuming my work on Cypress after 8 months hiatus. I upgraded the version to V 10.0.0. I see there's a lot of changes in the UI. Please suggest a best place to start learning about the changes and how I can still reuse my tests written in version 7.

Did you use this already? https://docs.cypress.io/guides/references/migration-guide

@fancy-airplane-60156 I would recommend starting at the changelog - https://docs.cypress.io/guides/references/changelog#10-4-0 I have also seen some great content from @nutritious-restaurant-91514 , @gray-kilobyte-89541 , @faint-spring-80499 and @most-carpenter-29893 around a few of these updates. I am sure they will share it in this thread 😀

I have a lesson more from a fresh start perspective : But it should help with understanding the new experience so you can later follow a migration process that works for you 🌹

Thank you so much. Let me check this now.

The testrail cli tool though is using python but works like a charm. No need to indicate the test case id on the scenario and auto uploads test cases and results 🙂

Hello, I am getting cucumber preprocessor plugin error on migrating to 10.0 version

Cucumber

I am trying to migrate to 10.0 version but I am not getting migration helper option., which will migrate config to new version. Any pointers?

are you running

cypress open

? What do you see when you do?

Hi everyone. Is there a way to pass devServer using the Cypress node API?

Hi all, after upgrading Cypress from 9.7.0 > 10.7.0 I see this error when I run commands: Is this error familiar? My node version is 16.17.0

Error [ERR_LOADER_CHAIN_INCOMPLETE]: 
"file:///Users/test/Library/Caches/Cypress/10.7.0/Cypress.app/Contents/Resources/app/node_modules/ts-node/esm/transpile-only.mjs 'resolve'" did not call the next hook in its chain and did not explicitly signal a short circuit. If this is intentional, include `shortCircuit: true` in the hook's return.
    at new NodeError (node:internal/errors:387:5)
    at ESMLoader.resolve (node:internal/modules/esm/loader:852:13)
    at async ESMLoader.getModuleJob (node:internal/modules/esm/loader:431:7)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:533:24)
    at async loadESM (node:internal/process/esm_loader:91:5)
    at async handleMainPromise (node:internal/modules/run_main:65:12) {
  code: 'ERR_LOADER_CHAIN_INCOMPLETE'
}

I reckon you've hit this open bug with Node 16.17.0 https://github.com/cypress-io/cypress/issues/22795 The workaround is to run Node version 16.16.0

Thanks, checking...

hey guys, when running tests in ci using 10.0.0 I get the following errors, does anyone know if there is a work around/fix for it

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [16299:0908/130819.131787:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process. [16299:0908/130819.139899:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

seems like the issue is with electron/default browser

switching the browser fixed the issue

Hello, I have migrated to cypress latest version and trying to execute in dashboard on chrome and edge browser execution gets stuck on first test itself, I have logs where it says browser not installed. Anybody facing same issue? What is the solution?

Hi All, Just have attempted migration on a monorepo moving cypress 9 -> 10 with applications using vite and vue 3. A behaviour that was working before was resolving a vite config that included aliasing paths e.g.

ts
export default defineConfig({
  // ...
  resolve: {
    extensions: ['.ts', '.js', '.json'],
    alias: {
      '@this-lib': path.resolve(__dirname, './src'),
      '@other-lib': path.resolve(__dirname, '../other-lib/src'),
    },
  },
});

But when running the spec file

Test.spec.ts

below:

ts
import { SomeEnum } from "@other-lib/SomeEnum";

describe('test', () => {
  it('should work', () => {
    cy.log('test' + SomeEnum.Cow);
  });
});

I get the output:

The following error originated from your test code, not from Cypress.

> Failed to fetch dynamically imported module: http://localhost:8080/__cypress/src/src/specs/Test.spec.ts

When Cypress detects uncaught errors originating from your test code it will automatically fail the current test.

Cypress could not associate this error to any specific test.

We dynamically generated a new test to display this failure.

This was resolving aliasing with version 9 of cypress and I'm trying to figure out why this is no longer the case

Cypress config looks like:

ts
export default defineConfig({
  ...cypressComponentConfig,
  projectId: '3FAxCE',
  component: {
    specPattern: '**/*.spec.ts',
    excludeSpecPattern: '**/*.{json,js}',
    supportFile: 'src/support/index.ts',
    indexHtmlFile: 'src/support/index.html',
    devServer: {
      bundler: 'vite',
      framework: 'vue',
    },
  }
});

I have tried with

viteConfig

property importing the

vite.config.ts

to no avail

Hi .... After upgrading to 10.3.0 version, I have observed tremendous speed improvements on local run on MacBook Pro M1. But does anyone have feedback about speed improvements on CI run which is Linux / Unix based server?

Hi After upgrading to 10 3 0 version I

Cypress config looks like