I have been using selenium for about a year, when I tried Cypress I was very impressed with the speed, it's like replacing an old car engine with a sports car engine 😂
I've worked and created enterprise level automation framework in Java using Selenium, TestNG, POM model, SerenityBDD, CucumberBDD. When I tried Cypress & Playwright, I found Cypress quick to start, offering similar depth and breadth in capabilities. I don't see myself going back to Selenium. If you're sufficiently skilled; you can automate almost everything web related in Cypress. Plus points for coding in JS/TS which has so many npm libraries which can be easily integrated.
i feel cucumber bdd framework is very complex even for simple tasks to automate and takes lot of time and skill is needed for coding..any other alternatives?
@@abhishekkumar-jw6rl Selecting CucumberBDD makes sense if the entire organization needs to standardize the automation, requirements and reporting process. For projects which are isolated and independent, Selenium with TestNg using POM approach works really well. You can integrate with majority CI/CD tools. I would however recommend you give Cypress a try. It's game changing.
@@zshn i am mediocre in coding..and switched recently to automation project. i feel our cucumber bdd framework in current project is very complex and all we do is manual testing for releases or sprints...i dont know whats use writing such huge framework when at end of day all is done manual only..is cypress better or easy to learn compared to cucumber bdd-pom-selenium javaa??
@@abhishekkumar-jw6rl Cypress definitely requires more experience. It's good that the framework you have is huge and not beneficial. The opportunity for you to make changes, improve and gain knowledge of 'how not to do' things is huge. I'd suggest you start with most critical workflows/TCs and break down larger files into smaller ones. Start by getting 20% of the tests run reliably and consistently. Show the mgmt the amount of hours you saved by optimizing. Move to lead role and focus on people & mgmt.
@@zshn problem is no proper people to guide...i feel if i would have been good in coding definitely would have become a developer...i feel learning coding or scripting is waste of time for testers..as u know majority of cases cannot be automated..like financial transactions or verifying generated PDF reports..etc...writing hundreds or thousand lines of code just to verify simple web elements is not worthfull right??....
Short and clear content. Seems a valuable channel. I hope to see some tutorials related to Cypress, Playwright framework, and API, because most tutorials are based on hard-coded data but not real-life websites and examples.
The basic question is that does Cypress handle with multiple browser tabs or just only one? If we have in our application link which is opened into separate browser tab and we want to switch there.
Hi raghav, actually I searched for selenium Ruby there are no such videos in TH-cam so if you start selenium with Ruby it will be good to learn from you
Hi Raghav...Being working as QA for 8 years..i feel selenium java with cucumber BDD, POM is very complex and difficult to handle and is unnecessary stress for testers..we have very complex framework in our project..but it doesnt handle any main business scenarious..i feel this framework is waste of time and unproductive...and i am a mediocre in coding. Any alternatives to this?..any code-less automation tools??..or it better to go for performance testing?
Both Selenium and Cypress are great tools for web automation testing, but for a beginner with manual testing experience and coding fear, I would recommend starting with Cypress. Here's a breakdown of why: Cypress: Simpler Syntax: Uses JavaScript code syntax similar to natural language, making it easier to understand and write tests compared to Selenium's more technical syntax. Built-in Features: Offers built-in features like waiting mechanisms, data assertions, and network interception, reducing the need for complex coding and external libraries. Fast Feedback: Provides real-time visual feedback with screenshots and recordings of test execution, aiding in understanding test failures. Large Community: Has a large and active community with extensive documentation, tutorials, and troubleshooting resources. Selenium: More Flexibility: Offers a wider range of languages and tools for advanced customization and integrations. Cross-Browser Testing: Supports testing across various browsers, while Cypress mainly focuses on Chrome. Greater Community Support: Has a longer history and a larger overall community, potentially offering more diverse solutions and knowledge bases. However, Selenium also comes with: Steeper Learning Curve: Requires learning various languages, frameworks, and tools, which can be overwhelming for beginners. More Code Writing: Often needs more complex coding constructs and external libraries, making it less ideal for those averse to coding. Slower Feedback: Debugging test failures might involve manually analyzing logs and debugging scripts. Considering your specific situation: 5 years of manual experience: This gives you a strong understanding of web applications and testing concepts, which can be easily translated to Cypress for automation. Coding fear: Cypress's simpler syntax and built-in features can help you ease into automation gradually without extensive coding. Additional tips: Start with basic tutorials and examples: Both Cypress and Selenium have plenty of beginner-friendly resources. Practice by automating simple tasks: Focus on automating small, manageable tasks in your current testing workflow to build confidence. Join the community: Utilize the active online communities for both tools to ask questions, learn from others, and find support. Remember, the best tool for you depends on your specific needs and preferences. While Cypress is generally easier to learn for beginners, if you need cross-browser testing or extensive customization, Selenium might be a better fit in the future. Start with Cypress to overcome your coding fear, and you can always explore Selenium later if needed
Hello Raghava, I am working as a Manual Testing Engineer, and now I am planning to learn Cypress. Can you suggest to me the best site where I can learn Cypress on my own?
Hi Vinod, if you like my way of teaching, can follow my cypress tutorials here - automationstepbystep.com/ Or you can follow Cypress Official Documentation -
We are mainly working on API with rest assured Cucumber Java combination. Also we use IBM mq and oracle DB for validation . Is it wise to switch from rest assured to Cypress. What I observed is Cypress is mainly used for UI. As all of my Dev work happened in Java but Is it wise to test through JS based cypress for API validation.?
Mohan Whether or not it is wise to switch from Rest Assured to Cypress for API validation depends on your specific needs and requirements. Rest Assured is a Java-based API testing framework that is known for its simplicity and ease of use. It is a good choice for simple API testing scenarios. However, it can be difficult to use for more complex scenarios. Cypress is a JavaScript-based end-to-end testing framework that is known for its flexibility and power. It is a good choice for complex API testing scenarios, as well as for UI testing. However, it can be more difficult to learn and use than Rest Assured. If you are mainly working on API testing with Rest Assured and Cucumber Java, and you are happy with the results, then there is no need to switch to Cypress. However, if you are looking for a more powerful and flexible API testing framework, then Cypress is a good option.
Hi RAGHAV in my current project I worked with cypress almost 8 months now that project is completed so now my manager move me to project which use selenium with java so it is better to stick with Cypress or should I move to selenium ?
Hi Nikhil, I believe it's good, you already have Cypress skill now, you can explore more and add more skills, Just that keep in touch with Cypress updates. I will plan to add new updates on this channel from time to time
Yes, both Playwright and Cypress support testing in Safari using WebKit Cypress Support for WebKit Cypress 10.8 introduced experimental support for testing in WebKit, which is the same browser engine used in Safari. To enable WebKit support in Cypress, you need to set the experimentalWebKitSupport config option to true in your cypress.config.ts file: import { defineConfig } from 'cypress'; export default defineConfig({ experimentalWebKitSupport: true, }); You can then run your Cypress tests using WebKit by specifying the browser option in your cypress.run command: npx cypress run --browser webkit Playwright Support for WebKit Playwright also supports testing in WebKit through its playwright-webkit package. You can install it using npm: npm install playwright-webkit To use WebKit with Playwright, you need to launch the WebKit browser instance using the playwright-webkit package: const playwright = require('playwright-webkit'); (async () => { const browser = await playwright.webkit.launch(); const context = await browser.newContext(); const page = await context.newPage(); // Your test code here await page.close(); await context.close(); await browser.close(); })(); Running Tests in WebKit using GitHub Actions You can also run your tests in WebKit using GitHub Actions. Here's an example workflow file: name: ci on: [push] jobs: tests: runs-on: ubuntu-20.04 steps: - name: Checkout uses: actions/checkout@v3 - name: Cypress run uses: cypress-io/github-action@v4 with: build: npm run lint start: npm run start-quiet browser: webkit Note that you need to install the required Linux libraries to run WebKit on GitHub Actions. You can do this by adding a playwright install-deps webkit command to your workflow file. In summary, both Playwright and Cypress support testing in Safari using WebKit, with some configuration and setup required -
Hi Raghav ! We are looking for setting up an automation framework for regression . We are upgrading our application to react pages. Can we use cypress for regression ? We already have selenium regression.
Kavya Yes, you can definitely use Cypress for regression testing your React application, even if you already have Selenium regression tests in place. While both are automation frameworks, they have distinct advantages and considerations for React testing: Cypress: Built specifically for modern web applications: Cypress is designed for testing single-page applications (SPAs) like React apps with its direct DOM manipulation and access to application state through DevTools. It integrates seamlessly with the browser environment, offering faster test execution and easier debugging. Command chain with assertions: Cypress utilizes a readable, single-threaded testing style with chained commands and built-in assertions. This makes test code more concise and easier to maintain compared to Selenium's step-by-step approach. Time travel debugging: Cypress allows you to "time travel" through your test steps, revisiting previous states of the application and inspecting elements during execution. This is immensely helpful for pinpointing issues. Automatic waiting: Cypress automatically waits for elements to become available before interacting with them, eliminating the need for explicit waits like Selenium's implicit Waits. This leads to more reliable and faster tests. Selenium: Wider browser compatibility: Selenium supports a broader range of browsers compared to Cypress, which currently focuses on Chrome and Chromium-based browsers. This might be important if you need to test across multiple browsers. Rich ecosystem of plugins: Selenium boasts a vast ecosystem of plugins and libraries for various functionalities and specific frameworks like React. This can be advantageous if you require specific testing capabilities not readily available in Cypress. Established framework: Selenium is a more mature and established framework with a larger community and more extensive documentation. This can be helpful for finding resources and troubleshooting issues. Migrating from Selenium to Cypress for React: Review existing tests: Evaluate your existing Selenium tests and identify those suitable for migrating to Cypress. Focus on tests specific to the React application logic and user interface. Start with simple tests: Begin by migrating straightforward tests first to get familiar with Cypress syntax and capabilities. This will help you gain confidence and build momentum for further migration. Utilize Cypress features: Leverage Cypress's unique features like time travel debugging and automatic waiting to improve your tests' speed and maintainability. Consider hybrid approach: You can maintain both Selenium and Cypress tests until you're fully comfortable with the migration. This lets you gradually transition while ensuring coverage. Conclusion: Cypress can be a valuable tool for your React regression testing, offering efficient and flexible testing with its modern features and seamless integration with SPAs. Consider reviewing your existing Selenium tests, starting with simple migrations, and utilizing Cypress's unique strengths to make a smooth transition while improving your overall testing experience. Remember, the best choice ultimately depends on your specific needs, team expertise, and desired balance between browser compatibility and framework features.
Hi, cypress is a node package and you will be creating a node project for cypress automation, so there package.json file will take care of dependencies like Maven in java projects
Here are some tips on how to start learning automation: 1. *Choose a programming language.* The most popular programming languages for automation are Python, Java, and JavaScript. Choose a language that you are interested in learning and that is in high demand in the job market. 2. *Learn the basics of automation.* There are many resources available online and in libraries that can teach you the basics of automation. Once you have a basic understanding of automation, you can start practicing by writing simple scripts. 3. *Choose an automation framework.* There are many automation frameworks available, such as Selenium, Appium, and Cypress. Choose a framework that is appropriate for the type of automation that you want to do. 4. *Start practicing with real-world applications.* Once you have learned the basics of automation and chosen an automation framework, you can start practicing with real-world applications. This will help you to learn the specific challenges of automating real-world applications. Here are some additional tips: *Start small.* Don't try to automate everything at once. Start by automating small, simple tasks. Once you have mastered automating simple tasks, you can move on to more complex tasks. *Use the right tools.* There are many tools available to help you automate. Choose the tools that are right for you and your needs. *Be patient.* It takes time and practice to learn automation. Don't get discouraged if you don't get it right away. Keep practicing and learning, and you will eventually become a proficient automation tester. I hope this helps
@@RaghavPal Thank you very much ! So I need to start learning a programming language. I started 1 week ago with JavaScript, but some friend told me, that I need to stop this and learning html and CSS. Because this things, he learned 4 years ago when he shwitched to Automation. He told me that I don't need to learn a programming language. In conclusion, do I need ar not to learn a programming language ?
Hello Sir, Can you please help with a Cypress scenario where the new tab button doesn't have a 'target' attribute. I need to open the new tab URL in the current tab instead. Thanks much!
Hi Raghav, I have completed the performance testing course using jmeter and load runner.What next course I can take to fulfill as a performance test engineer.Thanks.
HI Raghav can you please teach us how to automate authenticated api's in Cypress using page object model. Can you please show us an example in which you get (return token) token from sign up POST api and use it in some other class or page for next api. I am able to get that token on same page in same class but facing issue when trying to get on some other class/page.
Okay, so from a general point of view, when it comes to performance testing of batch jobs, there are specific parameters and considerations you should keep in mind. Let's explore how to approach performance testing for batch processes: 1. Throughput: - In a batch scenario, throughput is crucial. It refers to the rate at which tasks (workers or threads) can process data. - Identify how much throughput an individual worker can achieve. This helps you accurately size your production batch jobs based on batch size. - If throughput is not at an acceptable level, investigate areas such as query performance, indexes, and connection pools to improve logic and I/O efficiency 2. Endurance: - Ensure that your batch jobs can run consistently over an extended period. - Test the endurance of your system by running batch jobs with varying batch sizes. - If performance degrades as batch size increases, there might be bottlenecks that need fixing before handling large batches 3. Metrics to Collect: - Define relevant metrics to collect during performance testing. These may include: - Execution Time: Measure the time taken to process a batch. - Resource Utilization: Monitor CPU, memory, and disk usage. - Throughput: Calculate the number of records processed per unit of time. - Error Rate: Track any failures or exceptions. - Database Metrics: Check database response times, locks, and connection pool usage. 4. Test Data Setup: - Determine the test data requirements for your batch job. - Set up an isolated batch testing environment with representative data. - Consider data dependencies and methods to create test data Remember, batch performance testing focuses on throughput, endurance, and relevant metrics. By addressing these aspects, you can ensure your batch jobs perform optimally --
I am the manual tester..I don't have the any programming language knowledge..now I am moving to automation tester mean which automation tool is suites for me. And easy to learn pls suggest me..
If you are okay with the browser and language support in Cypress (as mentioned in this video), can give it a try. Can find all tutorials here - automationstepbystep.com/
Hi Raghav, I want to use same session across different spec, for that I am usinf testIsolation:false and also cacheAcrossSpecs: true, but still the session is not maintained, can you please let me know how to create session using cookies and maintain it across all the specs. Thanks!
Aditi To create a session using cookies and maintain it across all specs in Cypress, you can use the following steps: **1. Create a cookie jar** A cookie jar is a container that stores cookies. You can create a cookie jar using the following code: ```javascript const cookieJar = new Cypress.CookieJar(); ``` **2. Set the cookies** You can set cookies in the cookie jar using the following code: ```javascript cookieJar.setCookie('session_id', '1234567890'); ``` **3. Start a new Cypress spec** When you start a new Cypress spec, you can pass the cookie jar to the `cy.visit()` method. This will tell Cypress to use the cookie jar for the session. ```javascript cy.visit('example.com', { cookieJar }); ``` **4. Maintain the session across specs** To maintain the session across specs, you can use the following code: ```javascript // Get the cookie jar from the current spec. const cookieJar = cy.getCookieJar(); // Set the cookies in the cookie jar for the next spec. cookieJar.setCookie('session_id', '1234567890'); ``` You can call this code at the beginning of each spec that needs to use the existing session. Here is an example of a Cypress script that uses a cookie jar to maintain a session across specs: ```javascript // Create a cookie jar. const cookieJar = new Cypress.CookieJar(); // Set the session cookie. cookieJar.setCookie('session_id', '1234567890'); // Start a new spec and pass the cookie jar to the visit method. cy.visit('example.com', { cookieJar }); // Do some tests. // Maintain the session for the next spec. cookieJar.setCookie('session_id', '1234567890'); // Start a new spec. cy.visit('example.com', { cookieJar }); // Do some more tests. ``` This script will maintain the session across both specs, so that the user will not have to log in again.
Hi Suren The future of job opportunities in Cypress is uncertain. The current job market is tight, with many more people looking for work than there are jobs available. This is due in part to the COVID-19 pandemic, which has caused a number of businesses to close or reduce their workforces There are some positive signs for the future of job opportunities in Cypress. The state is home to a number of growing industries, such as technology, healthcare, and manufacturing. These industries are expected to create new jobs in the coming years However, there are also some challenges that could impact the future of job opportunities in Cypress. One challenge is the state's high cost of living. This could make it difficult for businesses to attract and retain employees. Another challenge is the state's aging population. This could lead to a decline in the number of workers available in the future Overall, the future of job opportunities in Cypress is uncertain. However, there are some positive signs that the state's economy is growing and that new jobs will be created in the coming years. Here are some tips for people who are looking for jobs in Cypress: * Network with people in your field. This is a great way to learn about job openings and to get your foot in the door. * Attend job fairs. This is another great way to meet potential employers and to learn about job openings. * Update your resume and cover letter regularly. Make sure your resume is tailored to each job you apply for. * Be prepared to interview. Practice answering common interview questions. * Don't give up. The job search can be tough, but it's important to keep trying.
Hi bro, you are doing great job. Giving knowledge in simple way. I need information about “MQTT protocol and It’s working in Jmeter”. If we need test MQTT Based application by using Jmeter what and how we need to test. If possible please provide information. Than you very much for your efforts 🫡
Hi Thinh It will be a good skill set to add. Also today with most things online and globalization, location may not be a constraint. I will suggest, go for it
Hi Raghav, thanks for the video. In my project the application is in Angular, so they have recommended to check for Cypress or Playwright. I am not having much knowledge into both. could you help me to decide which is better and quick to start a POC. I have basic knowledge on JAVA and JavaScript
Hi sir...thanks for information.... please help me..I stucked in a java cucumber framework....I wrote valid xpth but my selenium doesn't perform any action in the UI element....I got an no such element exception but....i found 1 of 1 in inspector... please help me to get out from this....
Hi all..... I got it actually,the element is present in another tab of browser being the reason it's not performed any action so I used get window handles method...it's working... much appreciated for your support ❤️🥰
Hi, pls check the syntax of your test, also the naming convention of the test file, if you are using cypress 10+, it should be xxx.cy.js , unless you have changed in config files
Hi Suren After being a Cypress tester for 2 years, there are a number of different paths you can take. Here are a few ideas: *Move into a more senior role* As you gain more experience, you can move into a more senior role, such as a lead tester or a quality assurance engineer. In these roles, you will be responsible for managing and mentoring other testers, as well as developing and executing test strategies. *Specialize in a particular area of testing* There are a number of different areas of testing that you can specialize in, such as performance testing, security testing, or usability testing. By specializing in a particular area, you can become an expert in that area and command a higher salary *Transition into a different role within the software development lifecycle* After gaining experience as a tester, you may be interested in transitioning into a different role within the software development lifecycle. For example, you could become a developer, a product manager, or a project manager. These roles offer different challenges and opportunities, and they can be a great way to advance your career No matter which path you choose, it is important to continue learning and growing. There are a number of different ways to do this, such as attending conferences, reading books and articles, and taking online courses. By continuing to learn, you will stay up-to-date on the latest trends in testing and you will be able to make a significant contribution to your team. Here are some additional tips for progressing your career as a Cypress tester: *Get involved in the Cypress community* There are a number of different ways to get involved in the Cypress community, such as attending meetups, contributing to the open source project, or writing blog posts about Cypress. Getting involved in the community is a great way to learn from other Cypress users, share your knowledge, and build your reputation *Stay up-to-date on the latest Cypress features* Cypress is constantly being updated with new features. To stay up-to-date on the latest features, you can read the Cypress blog, follow Cypress on Twitter, or join the Cypress Slack channel *Build your skills in other areas of testing* Cypress is a powerful tool, but it is not the only tool that you need to be a successful tester. To be a well-rounded tester, you should also have skills in other areas of testing, such as manual testing, performance testing, and security testing. * **Network with other testers.** Networking with other testers is a great way to learn new things, share your knowledge, and find new opportunities. You can network with other testers by attending conferences, meetups, and online forums Hope this helps
A correction at 3:20, the command is npm install cypress and to get a specific ver npm install cypress@9.7.0
Hi bro, can you please make a video on Tosca Automation , whether it as good opportunities in IT industry
yes its good, but don't depend solely on one skill or platform
@@RaghavPal Thank you bro
Via IntelliJ It was as easy as pie to set up.
I have been using selenium for about a year, when I tried Cypress I was very impressed with the speed, it's like replacing an old car engine with a sports car engine 😂
Yes, Cypress is fast
One of the best comparisons on the web. Just in 11 minutes. Great job!
Glad it helped!
I've worked and created enterprise level automation framework in Java using Selenium, TestNG, POM model, SerenityBDD, CucumberBDD. When I tried Cypress & Playwright, I found Cypress quick to start, offering similar depth and breadth in capabilities. I don't see myself going back to Selenium. If you're sufficiently skilled; you can automate almost everything web related in Cypress. Plus points for coding in JS/TS which has so many npm libraries which can be easily integrated.
i feel cucumber bdd framework is very complex even for simple tasks to automate and takes lot of time and skill is needed for coding..any other alternatives?
@@abhishekkumar-jw6rl Selecting CucumberBDD makes sense if the entire organization needs to standardize the automation, requirements and reporting process. For projects which are isolated and independent, Selenium with TestNg using POM approach works really well. You can integrate with majority CI/CD tools. I would however recommend you give Cypress a try. It's game changing.
@@zshn i am mediocre in coding..and switched recently to automation project. i feel our cucumber bdd framework in current project is very complex and all we do is manual testing for releases or sprints...i dont know whats use writing such huge framework when at end of day all is done manual only..is cypress better or easy to learn compared to cucumber bdd-pom-selenium javaa??
@@abhishekkumar-jw6rl Cypress definitely requires more experience. It's good that the framework you have is huge and not beneficial. The opportunity for you to make changes, improve and gain knowledge of 'how not to do' things is huge. I'd suggest you start with most critical workflows/TCs and break down larger files into smaller ones. Start by getting 20% of the tests run reliably and consistently. Show the mgmt the amount of hours you saved by optimizing. Move to lead role and focus on people & mgmt.
@@zshn problem is no proper people to guide...i feel if i would have been good in coding definitely would have become a developer...i feel learning coding or scripting is waste of time for testers..as u know majority of cases cannot be automated..like financial transactions or verifying generated PDF reports..etc...writing hundreds or thousand lines of code just to verify simple web elements is not worthfull right??....
Short and clear content. Seems a valuable channel. I hope to see some tutorials related to Cypress, Playwright framework, and API, because most tutorials are based on hard-coded data but not real-life websites and examples.
Sure, will do Rimantas
Thank you for the overview. I'll check out your other videos on Cypress :)
Sure
The basic question is that does Cypress handle with multiple browser tabs or just only one? If we have in our application link which is opened into separate browser tab and we want to switch there.
Not in Cypress as of today
Hi raghav, actually I searched for selenium Ruby there are no such videos in TH-cam so if you start selenium with Ruby it will be good to learn from you
I will plan on it Vicky
should add Playwright in the comparison list, this one is awesome!
I will do
is playwright better than cypress?
I was interested in Cypress until I saw that Safari isn't supported
That is a deal breaker for me
Yes, thats the case as of now
I saw yersterday that in the new version is supported
Hi Raghav...Being working as QA for 8 years..i feel selenium java with cucumber BDD, POM is very complex and difficult to handle and is unnecessary stress for testers..we have very complex framework in our project..but it doesnt handle any main business scenarious..i feel this framework is waste of time and unproductive...and i am a mediocre in coding. Any alternatives to this?..any code-less automation tools??..or it better to go for performance testing?
Hi Abhishek, you can try less code tools like Katalon Studio
Good information, to decide best automation tool.
Thanks Bala
Cypress k liye kya aana chaiye, java or javascript
JavaScript will help Ajay. And you do not need to learn and know complete JavaScript, you can start on Cypress after getting some fundamentals of JS
What is sdet
Can you please share what required to learn
I will plan a session on this Narayana
Good video Raghav sir🤝👍
So nice of you Suraj
Hi Raghav great work here as well. Can we expect Nightwatch tutorials any time soon?.
Hi Ani, yes, I will plan Nightwatch js
something which has more features and a lot faster will definitely be not free. And internet explorer is gone now. so 2 more points to cypress😁😉
true Rajashekar, that why I tried to inform most of the major aspects that people would like to know and then they can decide
For beginners which one is good to choose..I have 5yrs of Manual experience and coding fear😢
Both Selenium and Cypress are great tools for web automation testing, but for a beginner with manual testing experience and coding fear, I would recommend starting with Cypress. Here's a breakdown of why:
Cypress:
Simpler Syntax: Uses JavaScript code syntax similar to natural language, making it easier to understand and write tests compared to Selenium's more technical syntax.
Built-in Features: Offers built-in features like waiting mechanisms, data assertions, and network interception, reducing the need for complex coding and external libraries.
Fast Feedback: Provides real-time visual feedback with screenshots and recordings of test execution, aiding in understanding test failures.
Large Community: Has a large and active community with extensive documentation, tutorials, and troubleshooting resources.
Selenium:
More Flexibility: Offers a wider range of languages and tools for advanced customization and integrations.
Cross-Browser Testing: Supports testing across various browsers, while Cypress mainly focuses on Chrome.
Greater Community Support: Has a longer history and a larger overall community, potentially offering more diverse solutions and knowledge bases.
However, Selenium also comes with:
Steeper Learning Curve: Requires learning various languages, frameworks, and tools, which can be overwhelming for beginners.
More Code Writing: Often needs more complex coding constructs and external libraries, making it less ideal for those averse to coding.
Slower Feedback: Debugging test failures might involve manually analyzing logs and debugging scripts.
Considering your specific situation:
5 years of manual experience: This gives you a strong understanding of web applications and testing concepts, which can be easily translated to Cypress for automation.
Coding fear: Cypress's simpler syntax and built-in features can help you ease into automation gradually without extensive coding.
Additional tips:
Start with basic tutorials and examples: Both Cypress and Selenium have plenty of beginner-friendly resources.
Practice by automating simple tasks: Focus on automating small, manageable tasks in your current testing workflow to build confidence.
Join the community: Utilize the active online communities for both tools to ask questions, learn from others, and find support.
Remember, the best tool for you depends on your specific needs and preferences. While Cypress is generally easier to learn for beginners, if you need cross-browser testing or extensive customization, Selenium might be a better fit in the future. Start with Cypress to overcome your coding fear, and you can always explore Selenium later if needed
Hello Raghava,
I am working as a Manual Testing Engineer, and now I am planning to learn Cypress. Can you suggest to me the best site where I can learn Cypress on my own?
Hi Vinod, if you like my way of teaching, can follow my cypress tutorials here - automationstepbystep.com/ Or you can follow Cypress Official Documentation -
Thank you. I like your way of teaching. I will follow them.
@@RaghavPal Is it enough to attend for interviews with your videos. Or do I need to learn with other videos.
Depends on the topic, if its complete or not
Wow Thank you Raghav 🙏
Most welcome Santosh
Can you please do a video on cypress with specflow
I will plan Deepa
Could you please make videos on Cypress api automation using POM?
I will plan on this
We are mainly working on API with rest assured Cucumber Java combination. Also we use IBM mq and oracle DB for validation . Is it wise to switch from rest assured to Cypress. What I observed is Cypress is mainly used for UI. As all of my Dev work happened in Java but Is it wise to test through JS based cypress for API validation.?
Mohan
Whether or not it is wise to switch from Rest Assured to Cypress for API validation depends on your specific needs and requirements.
Rest Assured is a Java-based API testing framework that is known for its simplicity and ease of use. It is a good choice for simple API testing scenarios. However, it can be difficult to use for more complex scenarios.
Cypress is a JavaScript-based end-to-end testing framework that is known for its flexibility and power. It is a good choice for complex API testing scenarios, as well as for UI testing. However, it can be more difficult to learn and use than Rest Assured.
If you are mainly working on API testing with Rest Assured and Cucumber Java, and you are happy with the results, then there is no need to switch to Cypress. However, if you are looking for a more powerful and flexible API testing framework, then Cypress is a good option.
Hi bro, can you please make a video on Tosca Automation
I will check and plan on it Sharan
Hi RAGHAV in my current project I worked with cypress almost 8 months now that project is completed so now my manager move me to project which use selenium with java so it is better to stick with Cypress or should I move to selenium ?
Hi Nikhil, I believe it's good, you already have Cypress skill now, you can explore more and add more skills, Just that keep in touch with Cypress updates. I will plan to add new updates on this channel from time to time
@@RaghavPal @Raghav thank you for your updates
So sad I have problem with my npm and openssl on windows, I would've loved to use cypress since it's faster.
Can try some remote system
Another Question. Can I use Cucumber with Cypress?
Yes, you can use Cucumber with Cypress
Many thanks Raghav 🙏👍
Most welcome
it can support safari by using webkit
Yes, both Playwright and Cypress support testing in Safari using WebKit
Cypress Support for WebKit
Cypress 10.8 introduced experimental support for testing in WebKit, which is the same browser engine used in Safari. To enable WebKit support in Cypress, you need to set the experimentalWebKitSupport config option to true in your cypress.config.ts file:
import { defineConfig } from 'cypress';
export default defineConfig({
experimentalWebKitSupport: true,
});
You can then run your Cypress tests using WebKit by specifying the browser option in your cypress.run command:
npx cypress run --browser webkit
Playwright Support for WebKit
Playwright also supports testing in WebKit through its playwright-webkit package. You can install it using npm:
npm install playwright-webkit
To use WebKit with Playwright, you need to launch the WebKit browser instance using the playwright-webkit package:
const playwright = require('playwright-webkit');
(async () => {
const browser = await playwright.webkit.launch();
const context = await browser.newContext();
const page = await context.newPage();
// Your test code here
await page.close();
await context.close();
await browser.close();
})();
Running Tests in WebKit using GitHub Actions
You can also run your tests in WebKit using GitHub Actions. Here's an example workflow file:
name: ci
on: [push]
jobs:
tests:
runs-on: ubuntu-20.04
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Cypress run
uses: cypress-io/github-action@v4
with:
build: npm run lint
start: npm run start-quiet
browser: webkit
Note that you need to install the required Linux libraries to run WebKit on GitHub Actions. You can do this by adding a playwright install-deps webkit command to your workflow file.
In summary, both Playwright and Cypress support testing in Safari using WebKit, with some configuration and setup required
-
Hello!, which is better, selenium or serenityBDD with thucydies(WebElementFacade)?
It depends, on project, requirements, team understanding etc. In case you need to follow BDD approach, then you may check Serenity BDD
You are great!
Greetings from Brazil o/
Thanks Samir
Could have included Playwright in comparison, Raghav.
same here
I will plan on it
Hi Raghav ! We are looking for setting up an automation framework for regression . We are upgrading our application to react pages. Can we use cypress for regression ? We already have selenium regression.
Kavya
Yes, you can definitely use Cypress for regression testing your React application, even if you already have Selenium regression tests in place. While both are automation frameworks, they have distinct advantages and considerations for React testing:
Cypress:
Built specifically for modern web applications: Cypress is designed for testing single-page applications (SPAs) like React apps with its direct DOM manipulation and access to application state through DevTools. It integrates seamlessly with the browser environment, offering faster test execution and easier debugging.
Command chain with assertions: Cypress utilizes a readable, single-threaded testing style with chained commands and built-in assertions. This makes test code more concise and easier to maintain compared to Selenium's step-by-step approach.
Time travel debugging: Cypress allows you to "time travel" through your test steps, revisiting previous states of the application and inspecting elements during execution. This is immensely helpful for pinpointing issues.
Automatic waiting: Cypress automatically waits for elements to become available before interacting with them, eliminating the need for explicit waits like Selenium's implicit Waits. This leads to more reliable and faster tests.
Selenium:
Wider browser compatibility: Selenium supports a broader range of browsers compared to Cypress, which currently focuses on Chrome and Chromium-based browsers. This might be important if you need to test across multiple browsers.
Rich ecosystem of plugins: Selenium boasts a vast ecosystem of plugins and libraries for various functionalities and specific frameworks like React. This can be advantageous if you require specific testing capabilities not readily available in Cypress.
Established framework: Selenium is a more mature and established framework with a larger community and more extensive documentation. This can be helpful for finding resources and troubleshooting issues.
Migrating from Selenium to Cypress for React:
Review existing tests: Evaluate your existing Selenium tests and identify those suitable for migrating to Cypress. Focus on tests specific to the React application logic and user interface.
Start with simple tests: Begin by migrating straightforward tests first to get familiar with Cypress syntax and capabilities. This will help you gain confidence and build momentum for further migration.
Utilize Cypress features: Leverage Cypress's unique features like time travel debugging and automatic waiting to improve your tests' speed and maintainability.
Consider hybrid approach: You can maintain both Selenium and Cypress tests until you're fully comfortable with the migration. This lets you gradually transition while ensuring coverage.
Conclusion:
Cypress can be a valuable tool for your React regression testing, offering efficient and flexible testing with its modern features and seamless integration with SPAs. Consider reviewing your existing Selenium tests, starting with simple migrations, and utilizing Cypress's unique strengths to make a smooth transition while improving your overall testing experience.
Remember, the best choice ultimately depends on your specific needs, team expertise, and desired balance between browser compatibility and framework features.
Hi raghav your Udemy course on cypress has any different from TH-cam series?
There are few extra topics, can check the contents
Hi Sir ,
Is there any build tool like maven we can use it for cypress and bdd implementation with cypress is possible?
Hi, cypress is a node package and you will be creating a node project for cypress automation, so there package.json file will take care of dependencies like Maven in java projects
@@RaghavPal Thank you Sir
Cypress+bdd is absolutely possible
I want to start learning Automation, but I don't know where to start ? Please, can you give me some guidness ?
Here are some tips on how to start learning automation:
1. *Choose a programming language.* The most popular programming languages for automation are Python, Java, and JavaScript. Choose a language that you are interested in learning and that is in high demand in the job market.
2. *Learn the basics of automation.* There are many resources available online and in libraries that can teach you the basics of automation. Once you have a basic understanding of automation, you can start practicing by writing simple scripts.
3. *Choose an automation framework.* There are many automation frameworks available, such as Selenium, Appium, and Cypress. Choose a framework that is appropriate for the type of automation that you want to do.
4. *Start practicing with real-world applications.* Once you have learned the basics of automation and chosen an automation framework, you can start practicing with real-world applications. This will help you to learn the specific challenges of automating real-world applications.
Here are some additional tips:
*Start small.* Don't try to automate everything at once. Start by automating small, simple tasks. Once you have mastered automating simple tasks, you can move on to more complex tasks.
*Use the right tools.* There are many tools available to help you automate. Choose the tools that are right for you and your needs.
*Be patient.* It takes time and practice to learn automation. Don't get discouraged if you don't get it right away. Keep practicing and learning, and you will eventually become a proficient automation tester.
I hope this helps
@@RaghavPal Thank you very much ! So I need to start learning a programming language.
I started 1 week ago with JavaScript, but some friend told me, that I need to stop this and learning html and CSS. Because this things, he learned 4 years ago when he shwitched to Automation. He told me that I don't need to learn a programming language.
In conclusion, do I need ar not to learn a programming language ?
Having basic concepts of programming and a programming language will help you and take you long way...
JavaScript is good
@@RaghavPal Thank you again for the response !
Another question: I need to learn html and CSS, beside JS ?
It will be good to add skills on HTML and CSS, however for creating Automation Testing Frameworks, it is not compulsory
How to do performance testing in windows application using Gatling
Hi Dhina, I have not done this, will need to check online
Hello Sir,
Can you please help with a Cypress scenario where the new tab button doesn't have a 'target' attribute. I need to open the new tab URL in the current tab instead.
Thanks much!
Hi Tom, will need to check on this
Hi Raghav, I have completed the performance testing course using jmeter and load runner.What next course I can take to fulfill as a performance test engineer.Thanks.
Hi, you can now try to handle different user scenarios and also study the performance test plan creation
Hello Sir..Our project is angular based application ..which tool preferred?
Can use Cypress, if you are okay with few limitations as shown in this video
@@RaghavPal thank you so much sir.. you're one of my biggest motivations
HI Raghav can you please teach us how to automate authenticated api's in Cypress using page object model. Can you please show us an example in which you get (return token) token from sign up POST api and use it in some other class or page for next api. I am able to get that token on same page in same class but facing issue when trying to get on some other class/page.
Hi, I will plan to add some sessions on this
@@RaghavPal thank you so much it will be very helpful
How to run batch jobs in performance testing
Rama
please specify the platform, tool, scenario
@@RaghavPal
This question comes from an interview point of view
And also PT types of testing sequence order follow
Okay, so from a general point of view,
when it comes to performance testing of batch jobs, there are specific parameters and considerations you should keep in mind. Let's explore how to approach performance testing for batch processes:
1. Throughput:
- In a batch scenario, throughput is crucial. It refers to the rate at which tasks (workers or threads) can process data.
- Identify how much throughput an individual worker can achieve. This helps you accurately size your production batch jobs based on batch size.
- If throughput is not at an acceptable level, investigate areas such as query performance, indexes, and connection pools to improve logic and I/O efficiency
2. Endurance:
- Ensure that your batch jobs can run consistently over an extended period.
- Test the endurance of your system by running batch jobs with varying batch sizes.
- If performance degrades as batch size increases, there might be bottlenecks that need fixing before handling large batches
3. Metrics to Collect:
- Define relevant metrics to collect during performance testing. These may include:
- Execution Time: Measure the time taken to process a batch.
- Resource Utilization: Monitor CPU, memory, and disk usage.
- Throughput: Calculate the number of records processed per unit of time.
- Error Rate: Track any failures or exceptions.
- Database Metrics: Check database response times, locks, and connection pool usage.
4. Test Data Setup:
- Determine the test data requirements for your batch job.
- Set up an isolated batch testing environment with representative data.
- Consider data dependencies and methods to create test data
Remember, batch performance testing focuses on throughput, endurance, and relevant metrics. By addressing these aspects, you can ensure your batch jobs perform optimally
--
I am the manual tester..I don't have the any programming language knowledge..now I am moving to automation tester mean which automation tool is suites for me. And easy to learn pls suggest me..
cypress is easier for beginner, just follow raghav video about cypress.. after you master it. try another framework ( selenium )
@@MovieMomentsReviewFilm Thankyou
If you are okay with the browser and language support in Cypress (as mentioned in this video), can give it a try. Can find all tutorials here - automationstepbystep.com/
Hi Raghav, I want to use same session across different spec, for that I am usinf testIsolation:false and also cacheAcrossSpecs: true, but still the session is not maintained, can you please let me know how to create session using cookies and maintain it across all the specs.
Thanks!
Aditi
To create a session using cookies and maintain it across all specs in Cypress, you can use the following steps:
**1. Create a cookie jar**
A cookie jar is a container that stores cookies. You can create a cookie jar using the following code:
```javascript
const cookieJar = new Cypress.CookieJar();
```
**2. Set the cookies**
You can set cookies in the cookie jar using the following code:
```javascript
cookieJar.setCookie('session_id', '1234567890');
```
**3. Start a new Cypress spec**
When you start a new Cypress spec, you can pass the cookie jar to the `cy.visit()` method. This will tell Cypress to use the cookie jar for the session.
```javascript
cy.visit('example.com', { cookieJar });
```
**4. Maintain the session across specs**
To maintain the session across specs, you can use the following code:
```javascript
// Get the cookie jar from the current spec.
const cookieJar = cy.getCookieJar();
// Set the cookies in the cookie jar for the next spec.
cookieJar.setCookie('session_id', '1234567890');
```
You can call this code at the beginning of each spec that needs to use the existing session.
Here is an example of a Cypress script that uses a cookie jar to maintain a session across specs:
```javascript
// Create a cookie jar.
const cookieJar = new Cypress.CookieJar();
// Set the session cookie.
cookieJar.setCookie('session_id', '1234567890');
// Start a new spec and pass the cookie jar to the visit method.
cy.visit('example.com', { cookieJar });
// Do some tests.
// Maintain the session for the next spec.
cookieJar.setCookie('session_id', '1234567890');
// Start a new spec.
cy.visit('example.com', { cookieJar });
// Do some more tests.
```
This script will maintain the session across both specs, so that the user will not have to log in again.
Thank you!
Most welcome
Thanks!
Thanks for the support Dario
Sir Video on playwright
I will do it
Less job opportunities in cypress how is the future ?
Hi Suren
The future of job opportunities in Cypress is uncertain. The current job market is tight, with many more people looking for work than there are jobs available. This is due in part to the COVID-19 pandemic, which has caused a number of businesses to close or reduce their workforces
There are some positive signs for the future of job opportunities in Cypress. The state is home to a number of growing industries, such as technology, healthcare, and manufacturing. These industries are expected to create new jobs in the coming years
However, there are also some challenges that could impact the future of job opportunities in Cypress. One challenge is the state's high cost of living. This could make it difficult for businesses to attract and retain employees. Another challenge is the state's aging population. This could lead to a decline in the number of workers available in the future
Overall, the future of job opportunities in Cypress is uncertain. However, there are some positive signs that the state's economy is growing and that new jobs will be created in the coming years.
Here are some tips for people who are looking for jobs in Cypress:
* Network with people in your field. This is a great way to learn about job openings and to get your foot in the door.
* Attend job fairs. This is another great way to meet potential employers and to learn about job openings.
* Update your resume and cover letter regularly. Make sure your resume is tailored to each job you apply for.
* Be prepared to interview. Practice answering common interview questions.
* Don't give up. The job search can be tough, but it's important to keep trying.
@@RaghavPal thanks sir 🙏 thank you so much for reply ….
Hi bro, you are doing great job. Giving knowledge in simple way. I need information about “MQTT protocol and It’s working in Jmeter”. If we need test MQTT Based application by using Jmeter what and how we need to test. If possible please provide information. Than you very much for your efforts 🫡
I will check and plan a session on this Santha
should i learn it or playwright sir? i am in vietnam and it is not popular :((
Hi Thinh
It will be a good skill set to add. Also today with most things online and globalization, location may not be a constraint. I will suggest, go for it
@@RaghavPal but sir , cypress does not support on many browser , only chrome but playwright is full of browser ... which is better ?
Can go for Playwright
Hi Raghav, thanks for the video. In my project the application is in Angular, so they have recommended to check for Cypress or Playwright. I am not having much knowledge into both. could you help me to decide which is better and quick to start a POC. I have basic knowledge on JAVA and JavaScript
Hi Saurabh, A video on this is coming tomorrow - th-cam.com/video/cixkQHNkoZ4/w-d-xo.html
Hi. Do You have Cypress Course on udemy?
not yet Julian
Hi sir...thanks for information.... please help me..I stucked in a java cucumber framework....I wrote valid xpth but my selenium doesn't perform any action in the UI element....I got an no such element exception but....i found 1 of 1 in inspector... please help me to get out from this....
Did you check whether the element is hidden / inside a frame?
can be the case, pls check Satya, also add some wait time
Hi all..... I got it actually,the element is present in another tab of browser being the reason it's not performed any action so I used get window handles method...it's working... much appreciated for your support ❤️🥰
when i try writing a simple test and i run it it says no test found, how do i fix it?
Hi, pls check the syntax of your test, also the naming convention of the test file, if you are using cypress 10+, it should be xxx.cy.js , unless you have changed in config files
@@RaghavPal thank you, now everything is working perfetly !
Cypress is a better choice it's easy to use it
Hi Shahzil, it depends on needs and requirements, as shown in the video
@@RaghavPal I agreed with you.
Playwright is the future.
Don’t bother with anything else.
Playwright is definitely a good platform and skill to add. But as I say the field we are in, we need to have multiple skill set
🔥🔥
thanks for watching
👍
:)
Hi Sir
tell me best non coding jobs plz
there are many, will need more details on this
@@RaghavPal yes Sir
I need noncoding it jobs .it's useful for me
there can be many roles like QA, BA, Admin, Data Analyst, etc www.shecancode.io/blog/10-non-coding-ittech-jobs
Road map after being cypress tester for 2 years
Hi Suren
After being a Cypress tester for 2 years, there are a number of different paths you can take. Here are a few ideas:
*Move into a more senior role* As you gain more experience, you can move into a more senior role, such as a lead tester or a quality assurance engineer. In these roles, you will be responsible for managing and mentoring other testers, as well as developing and executing test strategies.
*Specialize in a particular area of testing* There are a number of different areas of testing that you can specialize in, such as performance testing, security testing, or usability testing. By specializing in a particular area, you can become an expert in that area and command a higher salary
*Transition into a different role within the software development lifecycle* After gaining experience as a tester, you may be interested in transitioning into a different role within the software development lifecycle. For example, you could become a developer, a product manager, or a project manager. These roles offer different challenges and opportunities, and they can be a great way to advance your career
No matter which path you choose, it is important to continue learning and growing. There are a number of different ways to do this, such as attending conferences, reading books and articles, and taking online courses. By continuing to learn, you will stay up-to-date on the latest trends in testing and you will be able to make a significant contribution to your team.
Here are some additional tips for progressing your career as a Cypress tester:
*Get involved in the Cypress community* There are a number of different ways to get involved in the Cypress community, such as attending meetups, contributing to the open source project, or writing blog posts about Cypress. Getting involved in the community is a great way to learn from other Cypress users, share your knowledge, and build your reputation
*Stay up-to-date on the latest Cypress features* Cypress is constantly being updated with new features. To stay up-to-date on the latest features, you can read the Cypress blog, follow Cypress on Twitter, or join the Cypress Slack channel
*Build your skills in other areas of testing* Cypress is a powerful tool, but it is not the only tool that you need to be a successful tester. To be a well-rounded tester, you should also have skills in other areas of testing, such as manual testing, performance testing, and security testing.
* **Network with other testers.** Networking with other testers is a great way to learn new things, share your knowledge, and find new opportunities. You can network with other testers by attending conferences, meetups, and online forums
Hope this helps
@@RaghavPal thanks sir … 🙏