For those wondering the Integration folder is now depreciated in newer versions of Cypress, when you select E2E, after running cy:open, it will generate an e2e folder and there is where you will find the tests
@@LambdaTest The beginning of tutorial is little outdated (minus of a very fast-growing environment), but it's OK. Little help of stackoverflow and everything is working great :) To your knowledge: I don't know how to get "zsh" terminal, I don't understand how to work on localhost, I had "Build Error While Integrating Cypress Testing Library on Gitlab" while installing cypress-testing-library
My friend told me about this channel and guess what I'm in love with what they are doing😍 I'm a beginner in this field, this tutorial really helped me to learn about Cypress in detail❤ I'd appriciate if you guys can make a video on Cypress Mouse Commands😁
Hi Elle, Thanks for your kind words! The Cypress tutorial has all you need to learn Cypress in detail: czcams.com/video/jX3v3N6oN5M/video.html However, we have a dedicated video covering Cypress Mouse Commands as well: czcams.com/video/43pTrPA7CNY/video.html
Thanks a lot for this relevant info! This video helps me to have an overview of what I'm looking for, it's time to create my testing framework. After working several years with selenium and java for web applications, now I will try to implement cypress for react application so I'm excited to do that. I will use for e2e testing, I'm thinking to implement POM and Gherkin.
i am not able to see the Integration folder getting created, I think it's not supported by the latest Cypress versions, how to compare your video with latest Cypress version?
If you clone the repository, you will not able to find a match with the video. Because the repo has developed a lot through the contributions. My suggestion is to create a basic cypress project and follow along with the videos.
those folders are now depreciated in newer versions of Cypress, when you select E2E, it will generate an e2e folder and there is where you will find the tests
hi, i'm having an error @7:03 , right after i try to run the command, the console returns this error: > cypress-example-kitchensink@0.0.0-development cy:open > cypress open sh: cypress: command not found
Hi, can you help me. Chrome starts, Cypress starts but after choosing test, error: Sorry, we could not load: localhost:8080/todo Simillar error for every test.
Navya, To find HTML Elements Using Cypress Locators please refer to our earlier blog on How To Find HTML Elements Using Cypress Locators: www.lambdatest.com/blog/finding-html-elements-using-cypress-locators/
Hey there 👋🏻 This tutorial assumes some familiarity with JavaScript and web testing concepts, so it would be beneficial to have some prior experience with these topics before starting the tutorial. However, if you're new to JavaScript and web development, you can still follow along with the tutorial and learn as you go.
Hey there👋🏻, Cypress is not capable of automating desktop apps. Cypress is more about a web application automation framework. This means if the application can run in a browser, Cypress can automate it.
I am facing the following error : Whenever I run the spec file or project in my local it is working fine and reports are also generating properly......But when i run it on Lambdatest - it is giving me error of " Cannot find module 'cypress- mochawesome-reporter/plugin '......I did all the possible solutions to resolve this but still showing this error not able to run the script on Lambdatest..... kindly please help on this
Hi Akshay, Please ensure cypress-mochawesome-reporter is correctly installed and imported in your Cypress plugins file, and that the node_modules directory is properly built on LambdaTest.
Hey there 👋🏻 Glad you liked it! Here are the steps to change your font in VS Code. Open your VS Code settings by clicking the gear icon in the lower left corner. Then, search for “Font Family” and type in “Cascadia Code”
Hi Sir, I have a button in the If I click that button it will open a new window. I am able to click button inside the frame but not able to replace the parent window/use the child window Please help
Hi Wasim, 1. make sure the frame is loaded correctly using this command: cy.frameLoaded('pass the locator of Frame') 2. Each time to access elements under the frame you must use "cy.()" then. If you are not using cy. , means Cypress access elements outside of the frame.
Hey Priya, You can define the global variables in the cypress.json file that is in your project root. Also check this out docs.cypress.io/guides/references/configuration
This is an error message I get for the opening scenario after installing lambatest to cypress framework. Is there anyone who could fix this? Environment variables also been applied ------------------- Checking Lambda Config in current directory Validating CLI validating config Error!! Cypress Config File does not exist
Hey Thilina 👋🏻 One of the main reason for this error could be cypress.json is not placed the root. Can you place the JSON file in the root of the project Or, you can pass the config file path parameter in your script
@@LambdaTest I ran to the same issue. But 1. The documentation said that cypress.json is now changed to cypress.config.js 2. I tried to point the parameter to cypress.config.js but after lambdatest-cypress run, I am receiving an error: Cypress.json is not parsed, please provide a valid json Error!! Cypress Config File does not has correct json 3. I tried creating cypress.config.json, so now I have both cypress.config.json and cypress.config.js, I tried github workflow and it works just fine but lambdatest gives me this error: There is both a cypress.json and a cypress.config.js at the location below: I don't have cypress.json file in my root directory. And all my configs are in the root directory also. Thank you for this tutorials btw. I am trying to finish this because I wanted to try taking your free cypress certificate. Kudos to you all!
Okay. After hours of searching and debugging, I finally figured it out. It all has to do on how the lambdatest-config.json is setup. 1. If you are using cypress v9, you are to explicitly use the cypress_config_file in run_settings. 2. If you are using Cypress v10 and above you just delete cypress_config_file in run_settings as it is automatically detected by lambdatest. If you add cypress_config_file and set it to the new config file, lambdatest-cypress run will till throw an error even if you use the --ccf flag. There's this note in the lambdatest documentation which says: Cypress 10 and above versions automatically identify the cypress.config.js file in the project. Therefore, you don't need to specify the cypress_config.js capability. I already read that prior to my hours of checking but somehow did not understand it right away. So for me, what I did is (I am using Cypress ^V10) I updated my lambdatest-config.json file as follows: 1. Deleted the cypress_config_file in my run_settings 2. Updated my npm_dependencies > cypress version to the correct one that I am using And there, I was able to get my test working.
Hi, If you are unable to find the cypress.json file in your project, it is possible that it hasn't been created yet or it might be located in a different directory. Make sure to save the cypress.json file in the root directory of your Cypress project to ensure it is recognized by Cypress.
The beginning of this video is super confusing. You just show your VScode with the code downloaded from your git repo, then you say that there is only one thing you need to do, which is cloning the repo, then you install Cypress ? Perhaps, it would be better for the beginners to show them everything step by step, so they can see the whole process. The Cypress folder never got created, it was already in the repo and it does not contain the integration folder. The structure is: cypress -> e2e -> 1-getting-started/2-advanced-examples Cypress dashboard looks completely different witj E2E Testing and Component Testing buttons - it does not give the user any opportunity to edit those tests. No explanation of what "it" does, what can be the alternatives placved there etc. I find this tutorial extremely un-useful.
Hey there, Thank you for taking the time to provide detailed feedback on the Cypress tutorial. We apologize for any confusion and gaps in the content Folder Structure Clarification: The structure cypress -> e2e -> 1-getting-started/2-advanced-examples is specific to the version and configuration of the Cypress setup in the tutorial. The standard Cypress installation creates a cypress directory with subdirectories like integration, fixtures, and support. The e2e directory is part of newer structures in Cypress 8 and later versions, focusing on end-to-end testing. Cypress Dashboard Updates: Cypress's UI does change over time with updates. The dashboard now differentiates between E2E Testing and Component Testing. For editing tests, you would typically do this within your code editor, not on the dashboard. The dashboard is more for viewing test runs, results, and configurations. Cypress Commands: The it command is used to define individual test cases in Mocha, which is the testing framework Cypress uses. Each it block represents a single test. Alternatives or variations include using describe to group multiple it test cases. If you have any more questions or need further guidance, please don't hesitate to reach out.
I got an error cy.visit() failed trying to load: / We failed looking for this file at the path: /Users/macintosh/Shahriyar/Cypressautomation/ The internal Cypress web server responded with: > 404: Not Found Because this error occurred during a before each hook we are skipping the remaining tests in the current suite: My First Test @LambdaTest can you please solve my problem.
@@LambdaTest Hi, any updates regarding this one? I'm also getting this error. For anyone still getting this error, it got solved on my side by adding 'baseUrl' , running a test, then changing it back to '/'. Not sure why it fixed it though :D . Please be advised that the config should look like this: e2e: { baseUrl: 'localhost:8080', }
Hey, Can you please check that you have sure your page is running healthy in localhost:3000? Maybe you can try to run a step first to make a request to this address and see if the status response is 200. Sometimes the reason could also be that cypress.json file was not in the root. Let us know if that helped :)
I so grateful about this course. I am facing this error pass two days and still haven't found solution. need urgent help. Error: read ECONNRESET { errno: -4077, code: 'ECONNRESET', syscall: 'read' } Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:211:20) Thank you so much
Zoe, The cause of this issue can be that the Cypress is getting blocked by anti-virus software. You can stop or pause your Antivirus and try. Also, update your Cypress version.
Hey Wasim, Cypress reload command help reload the page, is there any specific reason to look for an alternative? However, you can use window.location.reload()
great video! question, I got this error, how can I fix it? and Thank You! cy.visit() failed trying to load: localhost:8080/todo We attempted to make an http request to this URL but the request failed without a response. We received this error at the network level: > Error: connect ECONNREFUSED 127.0.0.1:8080
For those wondering the Integration folder is now depreciated in newer versions of Cypress, when you select E2E, after running cy:open, it will generate an e2e folder and there is where you will find the tests
Thanks Gabriel
after more than two hours I got to the 12th minute of this tutorial. So many things didn't work for me that I learned Cypess by myself to keep up: D
Hey Pawel 👋🏻,
Let us know how can we help.
@@LambdaTest The beginning of tutorial is little outdated (minus of a very fast-growing environment), but it's OK. Little help of stackoverflow and everything is working great :) To your knowledge:
I don't know how to get "zsh" terminal,
I don't understand how to work on localhost,
I had "Build Error While Integrating Cypress Testing Library on Gitlab" while installing cypress-testing-library
@@pawem.5160 Napięć swoją dupę, obejrzyj wideo, a następnie przeczytaj dokumentację, a będziesz szczęśliwy
My friend told me about this channel and guess what I'm in love with what they are doing😍 I'm a beginner in this field, this tutorial really helped me to learn about Cypress in detail❤ I'd appriciate if you guys can make a video on Cypress Mouse Commands😁
Hi Elle, Thanks for your kind words! The Cypress tutorial has all you need to learn Cypress in detail: czcams.com/video/jX3v3N6oN5M/video.html However, we have a dedicated video covering Cypress Mouse Commands as well: czcams.com/video/43pTrPA7CNY/video.html
Hi! Fellow Austinite here. Love this video!
Thanks 😊
Subscribe to our channel to never miss an update on the upcoming tutorials! ✨
Amazing classes! Congrats and thanks for the experience
Thanks Lucastep..Glad you liked it!
Thanks a lot for this relevant info! This video helps me to have an overview of what I'm looking for, it's time to create my testing framework. After working several years with selenium and java for web applications, now I will try to implement cypress for react application so I'm excited to do that. I will use for e2e testing, I'm thinking to implement POM and Gherkin.
Thanks for your kind words.Glad you liked it 😇
Make sure you subscribe to our CZcams channel for more 👋🏻
Cool, concise and informative. Thanks so much
Glad it was helpful!
Все четко и ясно. Хорошая связка.
Glad it was helpful.
Please subscribe to our CZcams channel for more such videos 🌟
great tutorial!
ty mate
Glad you liked it,
Subscribe to our channel for more such tutorials! ✨
i am not able to see the Integration folder getting created, I think it's not supported by the latest Cypress versions, how to compare your video with latest Cypress version?
If you clone the repository, you will not able to find a match with the video. Because the repo has developed a lot through the contributions. My suggestion is to create a basic cypress project and follow along with the videos.
those folders are now depreciated in newer versions of Cypress, when you select E2E, it will generate an e2e folder and there is where you will find the tests
Great tutorial!
Hey Jack 👋🏻
Glad you liked it! Subscribe for more✨
hi, i'm having an error @7:03 , right after i try to run the command, the console returns this error:
> cypress-example-kitchensink@0.0.0-development cy:open
> cypress open
sh: cypress: command not found
Hey Alejandro,
Let us get back to you on the same
Hey Alejandro, please try npm install cypress@latest --save-dev in your current folder
@@LambdaTest thank you! it worked :)
Hey pls tell me perquisites of this course
Hi Anashwar, you can find the prerequisite in this tutorial. However, do let us know if you are referring to any specific section/topic
Can you please add a video to talk about starting up localhost 8080?
That's a great suggestion!
Subscribe, and look forward to more tutorials! ✨
great stuff. thanks for the info.
Glad you found this helpful😊
Subscribe to our channel to never miss an update on the upcoming tutorials! ✨
Hello team? I am totally new to Cypress automation
Did I come to the right place ?
Yes!😊
Subscribe to our channel for more such tutorials! ✨
1:34:29
NICE VIDEO! VERY HELPFUL!
Just wondering why did you change findByPlaceholder into findByLabelText!
Hi, can you help me. Chrome starts, Cypress starts but after choosing test, error:
Sorry, we could not load: localhost:8080/todo
Simillar error for every test.
Hi Jacob, let us get back to you on this
HI Jakub, The Web Application is not configured in your local. Please change the application URL to "lambdatest.github.io/sample-todo-app/"
before running Cypress, make sure the localhost server is up and running, just type "npm start" on your project's terminal
@@alejandrosejas This was helpful for other scenarios too. Thanks
Could you guys help me understand how we can find HTML Elements Using Cypress Locators I'm stuck and I couldn't find it? 🙏
Navya, To find HTML Elements Using Cypress Locators please refer to our earlier blog on How To Find HTML Elements Using Cypress Locators: www.lambdatest.com/blog/finding-html-elements-using-cypress-locators/
Do you know how to get visual studio code on windows to accept mac style commands? I can't even install the project files without errors
Hey, Let us get back to you on this
@@LambdaTest thanks I've solved it. Needed to install git
Can you help me with how to write tests with Cypress UI commands? I have just started to learn cypress so it'd be very helpful 🤩
Nora, you can always check out our cypress playlist. Here is the link😊: czcams.com/video/jX3v3N6oN5M/video.html
Hope to contribute for the 1000 likes.
Make sure you subscribe to our CZcams Channel for more such tutorials! 🙌
Do u need to learn javascript for this tutorial or can i directly jump into this?
Hey there 👋🏻
This tutorial assumes some familiarity with JavaScript and web testing concepts, so it would be beneficial to have some prior experience with these topics before starting the tutorial. However, if you're new to JavaScript and web development, you can still follow along with the tutorial and learn as you go.
Can you share your vs code and vs code terminal theme plz ?
thank you for your tutorial is the automation of windows desktop applications also possible with this cypress tool?
cordially
Hey there👋🏻,
Cypress is not capable of automating desktop apps.
Cypress is more about a web application automation framework. This means if the application can run in a browser, Cypress can automate it.
I am facing the following error :
Whenever I run the spec file or project in my local it is working fine and reports are also generating properly......But when i run it on Lambdatest - it is giving me error of " Cannot find module 'cypress- mochawesome-reporter/plugin '......I did all the possible solutions to resolve this but still showing this error not able to run the script on Lambdatest..... kindly please help on this
Hi Akshay,
Please ensure cypress-mochawesome-reporter is correctly installed and imported in your Cypress plugins file, and that the node_modules directory is properly built on LambdaTest.
Your font looks good. How to get that? Is that an extension to be added in the project?
Hey there 👋🏻
Glad you liked it! Here are the steps to change your font in VS Code.
Open your VS Code settings by clicking the gear icon in the lower left corner. Then, search for “Font Family” and type in “Cascadia Code”
What is this vs code theme? Awsome content! :)
Thanks Matkotech👋🏻, Glad you liked it ✨
@@LambdaTest still do you know what vs code theme is this? ☺️
@@LambdaTest still do you know what vs code theme is this? ☺️
Hey Matkotech 👋🏻
Give us some time to get back with the details.
i have an error - missing script: "cy:open". why that?
Hey, Let us get back to you on this
Hey, Please try npm install cypress@latest --save-dev in your current folder
Anyway to fix the airy audio?
@paul, you mean the background noise? Also, if you can mention any particular time period where you are facing this, we will look into it. :)
Hi Sir,
I have a button in the
If I click that button it will open a new window.
I am able to click button inside the frame but not able to replace the parent window/use the child window
Please help
Hi Wasim, Let us get back to you on this
Hi Wasim,
1. make sure the frame is loaded correctly using this command: cy.frameLoaded('pass the locator of Frame')
2. Each time to access elements under the frame you must use "cy.()" then. If you are not using cy. , means Cypress access elements outside of the frame.
How to access global variable in cypress from another spec file.
Hey Priya,
You can define the global variables in the cypress.json file that is in your project root.
Also check this out docs.cypress.io/guides/references/configuration
This is an error message I get for the opening scenario after installing lambatest to cypress framework. Is there anyone who could fix this? Environment variables also been applied
-------------------
Checking Lambda Config in current directory
Validating CLI
validating config
Error!! Cypress Config File does not exist
Hey Thilina 👋🏻
One of the main reason for this error could be cypress.json is not placed the root. Can you place the JSON file in the root of the project
Or, you can pass the config file path parameter in your script
@@LambdaTest I ran to the same issue.
But 1. The documentation said that cypress.json is now changed to cypress.config.js
2. I tried to point the parameter to cypress.config.js but after lambdatest-cypress run, I am receiving an error:
Cypress.json is not parsed, please provide a valid json
Error!! Cypress Config File does not has correct json
3. I tried creating cypress.config.json, so now I have both cypress.config.json and cypress.config.js, I tried github workflow and it works just fine but lambdatest gives me this error: There is both a cypress.json and a cypress.config.js at the location below:
I don't have cypress.json file in my root directory.
And all my configs are in the root directory also.
Thank you for this tutorials btw. I am trying to finish this because I wanted to try taking your free cypress certificate. Kudos to you all!
Okay. After hours of searching and debugging, I finally figured it out.
It all has to do on how the lambdatest-config.json is setup.
1. If you are using cypress v9, you are to explicitly use the cypress_config_file in run_settings.
2. If you are using Cypress v10 and above you just delete cypress_config_file in run_settings as it is automatically detected by lambdatest. If you add cypress_config_file and set it to the new config file, lambdatest-cypress run will till throw an error even if you use the --ccf flag.
There's this note in the lambdatest documentation which says:
Cypress 10 and above versions automatically identify the cypress.config.js file in the project. Therefore, you don't need to specify the cypress_config.js capability.
I already read that prior to my hours of checking but somehow did not understand it right away.
So for me, what I did is (I am using Cypress ^V10) I updated my lambdatest-config.json file as follows:
1. Deleted the cypress_config_file in my run_settings
2. Updated my npm_dependencies > cypress version to the correct one that I am using
And there, I was able to get my test working.
Kindly share the github source code ?
Hey Muhammad
Please refer to this GitHub repo github.com/cypress-io/cypress-example-kitchensink
Hi! Good video. You mentioned repository link (Kitchen Sink) to clone and that it's in a description. But I can't see any... Cheers!
Hey Om, here's the repository link: github.com/cypress-io/cypress-example-kitchensink
@@LambdaTest Cheers! I found by googling it already. IT guys are smart 😜🧠
Very helpful. Thanks Chris (aka Ted Cruz's son)
Glad it was helpful!
i can not find cypress.json file
Hi,
If you are unable to find the cypress.json file in your project, it is possible that it hasn't been created yet or it might be located in a different directory. Make sure to save the cypress.json file in the root directory of your Cypress project to ensure it is recognized by Cypress.
You are Jesus to me!
Glad the video was helpful!
The beginning of this video is super confusing. You just show your VScode with the code downloaded from your git repo, then you say that there is only one thing you need to do, which is cloning the repo, then you install Cypress ? Perhaps, it would be better for the beginners to show them everything step by step, so they can see the whole process.
The Cypress folder never got created, it was already in the repo and it does not contain the integration folder. The structure is:
cypress -> e2e -> 1-getting-started/2-advanced-examples
Cypress dashboard looks completely different witj E2E Testing and Component Testing buttons - it does not give the user any opportunity to edit those tests.
No explanation of what "it" does, what can be the alternatives placved there etc.
I find this tutorial extremely un-useful.
Hey there,
Thank you for taking the time to provide detailed feedback on the Cypress tutorial. We apologize for any confusion and gaps in the content
Folder Structure Clarification: The structure cypress -> e2e -> 1-getting-started/2-advanced-examples is specific to the version and configuration of the Cypress setup in the tutorial. The standard Cypress installation creates a cypress directory with subdirectories like integration, fixtures, and support. The e2e directory is part of newer structures in Cypress 8 and later versions, focusing on end-to-end testing.
Cypress Dashboard Updates: Cypress's UI does change over time with updates. The dashboard now differentiates between E2E Testing and Component Testing. For editing tests, you would typically do this within your code editor, not on the dashboard. The dashboard is more for viewing test runs, results, and configurations.
Cypress Commands: The it command is used to define individual test cases in Mocha, which is the testing framework Cypress uses. Each it block represents a single test. Alternatives or variations include using describe to group multiple it test cases.
If you have any more questions or need further guidance, please don't hesitate to reach out.
I got an error
cy.visit() failed trying to load: / We failed looking for this file at the path: /Users/macintosh/Shahriyar/Cypressautomation/ The internal Cypress web server responded with: > 404: Not Found Because this error occurred during a before each hook we are skipping the remaining tests in the current suite: My First Test
@LambdaTest can you please solve my problem.
Hi Muhammad, let us get back to you on this
@@LambdaTest Hi, any updates regarding this one? I'm also getting this error. For anyone still getting this error, it got solved on my side by adding 'baseUrl' , running a test, then changing it back to '/'. Not sure why it fixed it though :D . Please be advised that the config should look like this: e2e: {
baseUrl: 'localhost:8080',
}
Hey, Can you please check that you have sure your page is running healthy in localhost:3000? Maybe you can try to run a step first to make a request to this address and see if the status response is 200. Sometimes the reason could also be that cypress.json file was not in the root. Let us know if that helped :)
I so grateful about this course.
I am facing this error pass two days and still haven't found solution. need urgent help.
Error: read ECONNRESET
{
errno: -4077,
code: 'ECONNRESET',
syscall: 'read'
}
Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:211:20)
Thank you so much
Hi Zoe, let us get back to you on this!
Zoe, The cause of this issue can be that the Cypress is getting blocked by anti-virus software. You can stop or pause your Antivirus and try. Also, update your Cypress version.
Hi
Is there any other way apart from cy.reload() to reload the page
Thanks in advancd
Hey Wasim, Let us get back to you on this
Hey Wasim, Cypress reload command help reload the page, is there any specific reason to look for an alternative?
However, you can use window.location.reload()
great video! question, I got this error, how can I fix it? and Thank You!
cy.visit() failed trying to load:
localhost:8080/todo
We attempted to make an http request to this URL but the request failed without a response.
We received this error at the network level:
> Error: connect ECONNREFUSED 127.0.0.1:8080
Hi Dan, The Web Application is not configured in your local. Please change the application URL to "lambdatest.github.io/sample-todo-app/"
before running Cypress, make sure the localhost server is up and running, just type "npm start" on your project's terminal
@@alejandrosejas Thank ya sir!