Yes I tried this as well. what i mean that when export the spec pattern (export CYPRESS_SPEC_PATTERN = "AnotherValue") it will not take the value it will keep it as is.

and only happened with this variable

and only happened with this variable

Hi everyone, I have an issue related to cypress 10.2.0 I want to ask about it, cypress is not reading specPattern value after exporting new value to it We have updated the version of the cypress from 9.7.0 to 10.2.0 recently, and we used to set the value of testFiles for Docker image using export CYPRESS_TEST_FILES=" some files or paths" Now the testFiles changed to specPattern, and when we use the same method, a new parameter is added to the env{} object, and the existing one outside the env{} object is still the same. Now we need a way to change the value of specPattern by exporting the value (we need to change it only in some cases, and not through cypress.config.ts) cypress.config.ts content: import { defineConfig } from 'cypress' export default defineConfig({ env: { webBaseUrl: 'http://localhost:4200', highlightColor: '#9ef11a', download_dir: '/cypress/downloads/', }, viewportWidth: 1680, viewportHeight: 1050, defaultCommandTimeout: 15000, reporter: 'mochawesome', video: false, retries: { runMode: 1, openMode: 1, }, reporterOptions: { reportDir: 'cypress/results', overwrite: false, html: false, json: true, }, e2e: { setupNodeEvents(on, config) { return require('./cypress/plugins/index.js')(on, config) }, baseUrl: 'https://localhost', specPattern: 'cypress/e2e/**/*.cy.ts', }, }) i tired: export CYPRESS_specPattern="cypress/e2e/**/*.spec.ts" then run cypress: in the settings are I got the data as in the attachment1 and the other specPattern value is shown in the attachment2 and it's clear that it's taking the second one into considerations any suggestions?

Hello, I upgraded cypress to the latest version 10.3.0 but still the same. I am not able to figure out the actual issue. It just hangs in the middle of the test.

Now I am getting this error in console

Greetings all, I am new to cypress. When i try to load config file "cypress open --config-file cypress/config/stage.config.json. it is asking me to make changes in cypress.config file which is already there. someone please suggest me the resolution. This was working in v9

That's frustrating. It does make me think "memory leak". Do you have any colleagues who see the same error when they run this test? If others can run it, perhaps you can improve the situation with

npm install

or

npm update

. Also, if you are doing anything unconventional in your tests (writing to console with every step) maybe try eliminating that stuff to see if it changes anything. You might also tinker with the soon-to-be-deprecated

nodeVersion

config option. https://docs.cypress.io/guides/references/configuration#Node-version

something in 10.3.0 sounded like a fix for this I've seen the same message, just restart cypress..

Hi all, I've upgraded to cypress 10.3.0, and when I start E2E in a browser (chrome, firefox, etc) via test runner, I see a blank browser instead of test specs. Has anyone encountered this problem or any suggestions why this could be happening?

can you please reproduce in a sharable repository? I cannot reproduce it

I use cypress for test driven dev, so I always have the IDE and cypress side by side like 40/60 but sometimes I enlarge cypress a little bit to have a better look at the browser (screenshot) My suggestion is to display the status line on the right side rather than the left (screenshot) That way I can see whether the test have passed or not without even switching to cypress

Hi everyone! I'm wondering is there a way to turn the dark theme off? The logs became unreadable for me, I literally see nothing only a wall of text. Also its hard to see the light blue text on dark blue background. This is especially important now, while the sun shines to my monitors Thx for the help in advance!

@late-planet-4481 was able to work around the issue by using the Stylebot extension https://chrome.google.com/webstore/detail/stylebot/oiaejidbmkiecgbjeifoejpgmdaleoha But I agree it would be nice to have a native solution for this. Even though the contrast passes a11y checks, it can still be hard to read in some contexts

Please don't @ people for an answer. Especially when it's the weekend

I waited for a week ago without any answer ! What do you expect me to do ? and what should i do ?

Well, @'ing several people with

?????

isn't the right way to approach this. Especially when no one is obliged to provide you with an answer Have you checked what comes up when you do

Cypress.env("specPattern")

? That will give you a definitive answer as to whether your environment variable is overriding what's in your config file. If it's showing the value set in your config file, rather than your environment variable, then that sounds like a bug. You can raise bugs here: https://github.com/cypress-io/cypress/issues

https://github.com/cypress-io/cypress/issues/22570 can someone help?

Having some trouble with migrating to V10. running the command

cypress open --browser chrome --e2e

or

cypress run chrome --e2e

runs without issue, and finds all the relevant spec files. But when I use a command which runs a js file:

CONFIG_FILE=qa1.mt1_all MARKET=all DEVICE=desktop node index.js

It cannot find the spec files, and returns the error:

Can't run because no spec files were found.

We searched for specs matching this glob pattern:

  > /Users/oiuasofd/code/oiuasodf/node/repo-name/cypress/e2e/**/*.cy.{js,jsx,ts,tsx}

The contents of index.js

const cypress = require('cypress');
const { v4: uuidv4 } = require('uuid');

cypress
  .run({
    browser: 'chrome',
    headless: true,
    record: true,
    parallel: true,
    ciBuildId: process.env.BUILD_ID || uuidv4(),
    key: 'randomly-generated-string', // This is a unique value for running parallel tests
    config: {
      env: {
        configFile: process.env.CONFIG_FILE || '',
        device: process.env.DEVICE,
        market: process.env.MARKET,
      },
    },
  })
  .catch(() => {
    process.exit(1);
  });

what kind of a file is

qa1.mt1_all

? What happens if you append .js / .ts to it?

that is a json file. I don't think anything good would happen if I appended .ts/.js to it 🙂

in cy 10, there's no more json config files we have to convert all that to js or ts

the migration handles the base cypress.json file, makes it into js or ts, but the ones under cypress/config folder you might have to do rewrite manually

I know all of that. I have a cypress.config.ts file which works together with the json file. As I stated above, all of these things work without issue, when running

cypress open --browser chrome --e2e

or

cypress run chrome --e2e

Well, I started a new migration on a fresh branch, this time allowing the migration wizard to perform its magic. And it works after that. I cannot tell what the difference is between doing manually and automatically, But I guess it must be human error.

Hi there, I decided to try out V10 (10.3.0) and I am having a few teething problems getting ui tests which previously ran successfully with V9.6.1 I completed the automatic migration as suggested. When running a script that opens a url from an app running locally on port 8080, the attached errors are recorded in the console and the test stops. Any ideas why this error might be occurring? Question: Does V10 support Angular web apps?

For the answer does it support Angular web apps I guess so because I am running my scripts against that architecture. For the other TS failure I think we need to see the

cypress.config.ts

to see whats going wrong.

I have again attempted to migrate to 10.3.0 from 9.3.0 but it is a stressful experience. I have renamed all my

_spec.js

to

cy.js

but I just get this when running from command line.

Can't run because no spec files were found.

We searched for specs matching this glob pattern:

Everything works fine when using the runner

Hello, Our product UI is build with ExtJS and to load the UI in the development environment takes around 30 - 60 seconds as we do not build the libraries(it does not happen in Production). When we used use version before Cypress 10, it used to take similar time to load the UI as that of doing it manually, but after upgrading to Cypress 10.3.0, it takes around 4 mins to load the UI. Its basically cy.visit() that takes so long time. We tried this on multiple development environments and we are seeing the exact behavior. Any idea how to debug this problem and identify the root cause ?

Make sure your run script is searching for specs in

/cypress/e2e/

not

/cypress/integration/