cypress: Cypress UI no longer displays spec files to run
Current behavior
From version 10.5.0 onwards, the specs section no longer displays any specs in the file.
However, when reviewing the project settings spec patterns, nine files can be found
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.
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
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 17 (8 by maintainers)
I can confirm that removing the component in cypress.config enabled it to run.
Removing the
componentsection from my config file worked for me, in both 10.5 and 10.6 - thanks a lot!I imagine a fix will be forthcoming so we don’t have to do that.
Which is fine with me; I had high hopes for using Cypress for component testing, but bailed on it as the setup - providing mocks/stubs for Vuetify and Vuex and Mirage - was just too daunting a task.
But that’s a whole 'nother issue. Thanks for all of the GREAT WORK that you folks do!
BTW, if people reading this haven’t checked out Mirage, you should. It’s a fake server that runs in the client, and lets front-end developers mock out backend APIs. It can be used in both development and testing, and it is fantastic! And it works with Cypress Integration tests to boot!
(For the record: I am not, and never have been, affiliated with Mirage in any way. I started out using Ember, and Mirage was built for that, which is how I got introduced to it. But they’ve since expanded it to work with React and Vue, the latter being what I now use.)
Thanks again!
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.devServerin the config… if you have partially set up component testing you might be in this state, and the workaround for now will be to removecomponentfrom your config - or set up yourdevServerwith the framework and bundler for component testing.If anybody still has the problem after modify the config, please post here with details.