question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cypress UI no longer displays spec files to run

See original GitHub issue

Current behavior

From version 10.5.0 onwards, the specs section no longer displays any specs in the file. image

However, when reviewing the project settings spec patterns, nine files can be found image

It should be noted that when the tests are run in headless mode, they continue to work as expected.

The current workaround is to downgrade to 10.4.0.

Desired behavior

After opening the cypress to use the UI format. Then selecting a browser types the spec files should display.

image

Test code to reproduce

const { defineConfig } = require(‘cypress’)

module.exports = defineConfig({ projectId: ‘f2y8fb’, chromeWebSecurity: false, responseTimeout: 60000, blockHosts: ‘.parsely.com’, pageLoadTimeout: 90000, e2e: { setupNodeEvents(on, config) { require(“cypress-grep/src/plugin”)(config); }, baseUrl: ‘https://www.teachstarter.com/’, //baseUrl: ‘https://staging-prexit.teachstarter.com/’, specPattern: 'cypress/e2e/teachStarterWeb/**/.{js,jsx,ts,tsx,spec}’, },

Cypress Version

10.5.0

Node version

v14.17.5

Operating System

Windows 11:22000.856

Debug Logs

No logs displayed

Other

No response

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:17 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
marktnoonancommented, Aug 22, 2022

After playing around a bit with the config files posted here, it looks like this error is due to a missing null check for component.devServer in the config… if you have partially set up component testing you might be in this state, and the workaround for now will be to remove component from your config - or set up your devServer with the framework and bundler for component testing.

If anybody still has the problem after modify the config, please post here with details.

1reaction
NUlmerTScommented, Aug 23, 2022

I can confirm that removing the component in cypress.config enabled it to run.

Read more comments on GitHub >

github_iconTop Results From Across the Web

New test file not showing in cypress UI - Stack Overflow
In this print-screen I have created a new file called: NewTest.spec.js (in green). It is not showing in Cypress. enter image description here...
Read more >
Troubleshooting | Cypress Documentation
Look at the video recordings and screenshots. Split large spec files into smaller ones. Split long tests into smaller tests. Run the same...
Read more >
Command Line - Cypress Documentation
To prevent Cypress from exiting after running tests in a spec file, use --no-exit . You can pass --headed --no-exit in order to...
Read more >
Configuration - Cypress Documentation
Using a .mjs file will allow you to use ESM Module syntax in your config ... the "Run All Specs" UI feature, allowing...
Read more >
Writing and Organizing Tests - Cypress Documentation
Configuring plugins via cypress/plugins/index.js is no longer supported as of ... beforeEach(() => { cy.log('I run before every test in every spec file!...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found