Thanks for the solution, Gleb! Regarding Cypress 10, are you going to update the cypress-grep and find-specs plugins to work with Cypress 10? I tested it and they don't work in this new Cypress version :(
Hi gleb, when I try to add the CI=1 under scripts in package.json like so "cy:run:qa": "npx cypress run CI=1 --e2e". it does not recognize the CI=1, can you recommend any workaround for this?
CI=1 is an environment variable, you should set it using the shell command when starting cypress. You cannot mix it with cypress arguments. Of course you can also read it from the cypress env values I think. I should record another video to show it
@@gleb thanks gleb, would love to watch that. it would defnitely look clean if there is a way that we can skip manually typing CI=1 in the shell command. awesome demo by the way.
Hi, I couldn't find any solutions of the problem; You are attempting to use Cypress with an older config file: cypress.json When you upgraded to Cypress v10.0 the config file was updated and moved to a new location: cypress.config.js You may need to update any CLI scripts to ensure that they are referring the new version. This would typically look something like: "cypress open --config-file=cypress.config.js"
1. Do not post the same unrelated question under multiple videos. 2. Could you ask your Cypress question at on.cypress.io/chat or on.cypress.io/discord or the specific repo via GH issues? It will be easier for your to provide code snippets, screenshots, etc to explain what you are trying to do. You could also help me answer Cypress-related questions faster by supporting me via GitHub sponsors github.com/sponsors/bahmutov, by buying my Cypress courses at cypress.tips/courses, or by inviting me to teach Cypress cypress.tips/workshops
@@gleb I had a rule in my automation team to run all specs localy before merge request, but now i guess the rule's going to be run the branch before pushing
![Chlöe - Shake (Feat. Jeremih) [Official Visualizer]](http://i.ytimg.com/vi/aDs_1ufpfv8/mqdefault.jpg)
I was searching for this couple of days! Thanks a lot :)
Thanks for the solution, Gleb!
Regarding Cypress 10, are you going to update the cypress-grep and find-specs plugins to work with Cypress 10? I tested it and they don't work in this new Cypress version :(
Eventually yes
@@gleb thanks for the reply :)
Excelente, muchas gracias! Thanks very much!!
Hi gleb, when I try to add the CI=1 under scripts in package.json like so "cy:run:qa": "npx cypress run CI=1 --e2e". it does not recognize the CI=1, can you recommend any workaround for this?
CI=1 is an environment variable, you should set it using the shell command when starting cypress. You cannot mix it with cypress arguments. Of course you can also read it from the cypress env values I think. I should record another video to show it
@@gleb thanks gleb, would love to watch that. it would defnitely look clean if there is a way that we can skip manually typing CI=1 in the shell command. awesome demo by the way.
@@lynyrdrossalquiroz2029 watch ruclips.net/video/butlgoP4SzI/видео.html
how can they forgot that button? This is so annoying? It is the most used button probably
They did not forget the button. The button was broken and if needed they can implement it correctly in the future.
I can put this import in one-line syntax? For not repeat the word import? I try here in array but doesn't work
No, the import keyword in JavaScript is pretty inflexible
Thanks very helpful 🙂
What file icon theme do you use?
vscode-icons I think
Hi, is there any solution how to run all specs for users who use cucumber / feature files as well? Thanks in advance.
Unfortunately I don't use cucumber syntax, so cannot tell
@@glebthanks. Can u do tutorial about how to use tags instead?
using cypress-grep? Sorry, don't understand
@@gleb I have managed to solve the issue. Successfully installed grep and run tests. Thanks.
So sad to have lost the Run All Specs feature. I wouldn't have updated if I had known.
Literally nothing stops you from going to any cypress version that you want. Just set to the exact version in package json and it is all good
@@gleb They need to put it back, this is ridiculous
Hi,
I couldn't find any solutions of the problem;
You are attempting to use Cypress with an older config file: cypress.json When you upgraded to Cypress v10.0 the config file was updated and moved to a new location: cypress.config.js
You may need to update any CLI scripts to ensure that they are referring the new version. This would typically look something like: "cypress open --config-file=cypress.config.js"
1. Do not post the same unrelated question under multiple videos.
2. Could you ask your Cypress question at on.cypress.io/chat or on.cypress.io/discord or the specific repo via GH issues? It will be easier for your to provide code snippets, screenshots, etc to explain what you are trying to do. You could also help me answer Cypress-related questions faster by supporting me via GitHub sponsors github.com/sponsors/bahmutov, by buying my Cypress courses at cypress.tips/courses, or by inviting me to teach Cypress cypress.tips/workshops
Can u do the video for parallel execution
I am not sure what you mean, on.cypress.io/parallelization?
can you give chance to get mock interview with you?
Mock interview?
I appreciate this, thank you, but they have to make that easier from the UX
I read their reason why, I sort of buy it, but it is still a pain in the butt. THANKS FOR THE INFO.. Appreciate it!
I have 100 spec files across 10 different folders, can't be bothered to do it, i'll stick to running the pipeline on my lbranch ;D
That’s the right course of action anyway. You don’t want to waste your time running all specs, let’s the CI do it for you
@@gleb I had a rule in my automation team to run all specs localy before merge request, but now i guess the rule's going to be run the branch before pushing
Is any way to do wild card
import './mytest/*.cy.ts'
I don't think so, but I might be mistaken