-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin fails to evaluate the configuration with Cypress 11 #110
Comments
What does it mean "cypress config selects this test"? My cypress.config.js contains nothing about selecting tests. I can run the test from the command line, both with the Cypress ui and without it. The gutter icon "cy" is not visible. |
Cypress can run only tests that are matched by Could you share you cypress configuration file or the whole project? Also, it would be nice if you collect the debug logs. |
Could I send the IntelliJ log through a private channel? |
yep, you can send an email to mikhail.bolotov at Gmail |
Does not seem to pick up |
while I'm still searching for a way to evaluate a configuration with Cypress 11, you can use this bundle and disable config parsing: When disabled, a run configuration can be created from a gutter as usual, though some other features that depend on the data from config may not be available in this mode. This mode is automatically enabled when Cypress 11 is detected: |
Hey guys, i have same problem with PHP Storm 2022.3 and Cypress 11. Is there workaround without Pro plugin? |
@bajzik |
3.5.1 is version of Pro plugin if I'm right, so also workaround above my comment is probably for Pro version. So I'm asking if there is workaround for free version. |
What's the problem with the free version? |
So it was working okay with Cypress 10 and not working with Cypress 11? |
I better say with 9. I was updating Cypress from 9.5.* version to 11. |
What's the name of your cypress configuration file? |
cypress.config.ts |
could you share your project? |
Project is using yarn workspaces, where vue is one of package/ws and tests are another package/ws. So cypress.config.ts is in this test package where also test files (cy.ts) are stored. |
did the configuration file change the location when you migrated from 9 to 11 version? |
Nope, files are still the same. I think that we renamed test.ts co cy.ts but it was while ago. Is there any example for run configuration? Or it's not necessary if we're not able to run in from cy.ts file |
anyway, I cannot reproduce the problem without a sample project |
Hi there! Note: Exercises are in Cypress 9, but I upgraded to latest (12). I tried to run a spec file after upgrading to Cypress 12 and it shows me a similar error:
UPDATE: |
I have the same issue with phpstorm where I cannot run individual tests from within the test files. here's a minimal reproducible example where I have this happening: https://github.com/scmppmcs/mre-cypress-phpstorm my issue when accessing any test icon dropdown: This is on an alma linux VM. This problem did not appear on other distro vms. Phpstorm is the snap version. One difference I saw with the other VM is that node is installed with snap but this one is not. When I create a test configuration to run a single test within a test file then run it, I get this in logs with the relevant debug log setting (#me.mbolotov.cypress:all):
If you have any suggestions on additional steps to debug this, please tell! |
hi @scmppmcs! |
hi @list4c! |
So I installed the zip and now it just works like I expect (I can run single tests from the gutter). Thank you so much! Here is the log when I run a single test: idea.log
|
Describe the bug
Running tests by clicking the gutter icon tries to run it as a Node.js run config, which fails.
Versions:
The text was updated successfully, but these errors were encountered: