#AskRaghav 

Hi Gabriel, hope this helps you

Thanks for sharing Elisa

Hi Elisa We also need to do a POC for comparing Cypress and Playwright for our application. Can you please help me with some strong points in favor of Playwright.

Sure, here are some strong points in favor of Playwright: * Cross-platform support: Playwright supports all major desktop and mobile platforms, including Windows, macOS, Linux, iOS, and Android. This makes it a good choice for projects that need to be tested across multiple platforms. * Headless mode: Playwright supports headless mode, which means that you can run your tests without actually opening a browser window. This can be useful for performance testing or for testing applications that are not designed to be used in a browser. * Network interception: Playwright allows you to intercept and mock network requests. This can be useful for testing applications that make API calls or for testing applications that are sensitive to network latency. * Comprehensive documentation: Playwright has comprehensive documentation that covers everything from getting started to advanced topics. This makes it easy to learn how to use Playwright and to find answers to your questions. * Active community: Playwright has an active community of users and contributors. This means that there is a lot of support available if you need help with Playwright. Ultimately, the best choice for your project will depend on your specific needs. If you need to test across multiple platforms or if you need to use headless mode, then Playwright is a good choice. If you are looking for an easy-to-learn tool with a large library of plugins, then Cypress is a good choice.

@@urvashigupta7291As far as I know, PW is much faster and one can write simple UI tests with code gen feature. ( I don't have idea about cypress here)

@@RaghavPal Thanks for mentioning these points Raghav!

Thanks for adding Ahamed

Cypress does have snapshot testing , what are you talking about ? . It works

Gaygachad, I didnt say that Cypress can’t do it. Just said that Playwright supports that too. Tell me any thing that can be done only in Cypress?

@@ahamedabdulrahman brother, help me with something. If my project manager tells me to use cypress for testing, who has basically zero knowledge about testing, how do I convince him that Playwright is better?

I understand this Domitori, and it's a valid point. However, in case of Cypress, the paid feature is completely an additional thing and in no ways impact the project. It's like is someone wants to take it for extra analytics and monitoring. Also, the users have a lot of options and can decide based on the requirements.

Couldn't agree more Vasanth

Always welcome Suraj

Selenium is not doubt mostly used and works well. There are some additional options and features. It will depend on your needs, project requirements, application requirements

Sure.. will plan

I will plan Naveen

Most welcome Mireya

Hi Hamid Both are good, It will depend on your needs and project, app requirmentments If you are looking for a framework that is easy to use and has a good range of features, then Cypress is a good option. If you need to test across multiple browsers and operating systems, then Playwright is a good choice. And if you are looking for a mature framework with a large community of users, then Selenium is a good option. There are many factors to consider when choosing a testing framework for modern software, such as the type of software you are testing, the features you need, and your team's experience level.

Ashwin Both Python and JavaScript are excellent choices for Playwright, and the "better" one really depends on your personal preferences and project needs In case you have no prior exp with any of the 2 and are open to use anything, I will suggest to check the first few videos of my Python and JavaScript playlist here - automationstepbystep.com/ This will help you Here's a quick comparison to help you decide: JavaScript: If you're more familiar with JavaScript or your project is heavily reliant on JavaScript technologies, then sticking with JavaScript might be a smoother experience Python: If you're already comfortable with Python or prefer its clean and readable syntax, then it's a great option. Playwright's Python API is well-documented and easy to pick up Ultimately, the best way to choose is to try both and see which one feels more natural to you. Playwright's core concepts are the same regardless of the language, so you can easily switch between them if needed -

It's Live now David

Mutasim I understand your struggle and I'm happy to help you convince your manager of your choice to stick with Playwright TypeScript for your current project. Here's how you can present your case: *Your Argument:* 1. *Focus on Flaky Tests:* Highlight the specific flaky test issues you faced with Selenium and how Playwright's improved stability addressed them. Provide concrete examples from your existing automation for their project. 2. *Leverage Existing Skills:* Emphasize your strong proficiency in both Java and TypeScript and how Playwright allows you to utilize both comfortably. 3. *Project Completion:* Explain how switching to a new tool like Cypress (unfamiliar to you) can introduce a learning curve and potentially delay project completion. 4. *Long-Term Benefits:* Briefly mention the benefits of Playwright beyond flaky tests, like cross-browser testing, mobile web testing, and desktop applications. This shows your strategic thinking and future-proofing the automation infrastructure. *Responding to Cypress:* 1. *Express Concerns:* Be honest about your discomfort with Cypress. Explain that, while it might be a good tool, starting from scratch with limited knowledge won't yield immediate benefits. 2. *Alternative Comparison:* If your manager insists on comparing tools, suggest looking at Playwright vs. Cypress side-by-side (features, performance, community support) instead of blindly bringing in a new option. *Additional Tips:* * *Prepare Data:* Gather data points like test execution times, flaky test rates, and developer hours saved using Playwright to quantify its positive impact. * *Offer Compromise:* If your manager remains keen on exploring Cypress, propose a small side project or sandbox environment to experiment with it without jeopardizing the current project's timeline. * *Keep It Professional:* Maintain a respectful and objective tone throughout the discussion. Focus on data and rationale rather than personal preferences. Remember, convincing your manager is about demonstrating the value you bring to the project. Your existing experience with Playwright, combined with a well-constructed argument showcasing its benefits, should help you stay on track. I hope this helps

@@RaghavPal God bless you my brother. You probably saved my job right there ❤️

Most welcome SineQuaNon

Hi Hamza Not at the moment

keep up the good work , from your experience which one is better in modern days

If there is no specific project requirement or need, Can learn Cypress 1st

@@RaghavPal thanks

Hi Samir Both Cypress and Playwright are popular alternatives to Selenium for web automation testing. The choice between the two depends on various factors, including your specific requirements and preferences. Here's some information to help you make a decision: Cypress: - Cypress is a JavaScript-based end-to-end testing framework. - It provides a simplified and intuitive API for writing tests. - Cypress has built-in features like time-travel debugging and automatic waiting, which make it easy to write and debug tests. - It runs directly in the browser, allowing you to see real-time changes and interactions with the application under test. - Cypress has excellent support for testing modern web applications built with frameworks like React, Angular, and Vue.js. - It has a vibrant and active community with extensive documentation and resources. Playwright: - Playwright is a JavaScript-based multi-browser automation library. - It provides a unified API to automate interactions with web browsers like Chrome, Firefox, and Safari. - Playwright offers cross-browser support, allowing you to write tests once and run them across different browsers. - It has powerful features like browser context isolation and network interception, which enable advanced testing scenarios. - Playwright is suitable for testing web applications across different platforms, including desktop, mobile, and headless browsers. - It supports multiple programming languages, including JavaScript, Python, and .NET.

Hi Ramesh, Yes, Playwright does support mobile web browsers. Playwright can be used to automate mobile web browsers such as Safari on iOS devices and Chrome on Android devices, in addition to desktop web browsers. To use Playwright with mobile web browsers, you will need to set up the appropriate browser and device contexts. Here's an example of how you can set up a mobile browser context in Playwright for iOS Safari: const { webkit, devices } = require('playwright'); (async () => { const iPhone11 = devices['iPhone 11 Pro']; const browser = await webkit.launch(); const context = await browser.newContext({ ...iPhone11, }); const page = await context.newPage(); // Use the page object to navigate to a URL and interact with the web page as needed await browser.close(); })(); In this example, we are creating a new mobile device context for an iPhone 11 Pro using the devices object from Playwright. We then launch a new instance of the webkit browser and create a new page in the context. From there, we can use the page object to navigate to a URL and interact with the web page as needed. You can also set up device emulation and geolocation using the context options. For more information, you can refer to the Playwright documentation on mobile web testing: playwright.dev/docs/mobile-testing/

Hi Ashish Here are some of the most popular automation testing tools: * Selenium: Selenium is a free and open-source automation testing framework. It is one of the most popular automation testing tools, and it is supported by a large community of developers. * Cypress: Cypress is a newer automation testing tool that is gaining popularity. It is known for its ease of use and its ability to write tests that are more readable and maintainable. * Playwright: Playwright is a newer automation testing tool that is developed by Google. It is a cross-platform tool that can be used to automate web and mobile applications. If you are already familiar with Java, then you could start by learning Selenium with Java. If you are not familiar with Java, then you could start by learning Python and then learning Selenium with Python. Once you have learned one of these tools, you can then start learning other tools. For example, you could learn Cypress after you have learned Selenium. Here is a possible career path for a manual tester who wants to become an automation testing engineer: * **Manual tester:** Start as a manual tester and gain experience in testing different types of software. * **Automation tester:** Learn automation testing and start automating some of the manual tests that you are currently doing. * **Senior automation tester:** Become a senior automation tester and lead a team of automation testers. * **Automation architect:** Become an automation architect and design and implement automation testing solutions. This is just one possible career path, and there are many other paths that you could take. The most important thing is to start learning automation testing and to gain experience in this field. I hope this helps

I am a web automation tester which one is best to learn feature Cypress or playwright

Anup Let me know if you are looking for a specific feature, functionality or scenario, In general, can check these: Katalon Studio Tricentis Tosca Testim Parasoft SOAtest Ranorex Functionize

Most welcome

Hi Chandra, If you are experiencing issues with the Cypress test runner not responding, there are a few things you can try to resolve the issue: Check for updates: Make sure you have the latest version of Cypress installed. You can check for updates by running npm outdated cypress in your project directory. Clear the cache: Sometimes the Cypress cache can cause issues with the test runner. You can try clearing the cache by running npx cypress cache clear in your project directory. Disable third-party antivirus software: Some antivirus software can interfere with Cypress and cause it to not respond. Try disabling any third-party antivirus software and see if the issue is resolved. Check system resources: Make sure that your system has enough resources (CPU, memory, etc.) to run Cypress. If your system is low on resources, it may cause Cypress to not respond. Try running the tests headlessly: If you are running Cypress with a graphical interface, try running the tests headlessly by adding the --headless option to the Cypress command. This can sometimes resolve issues with the test runner not responding. Try running the tests on a different machine: If the above solutions don't work, try running the tests on a different machine to see if the issue is specific to your local environment. If none of these solutions work, please provide more details about the specific error message you are seeing and any additional information about your setup that may be relevant

@@RaghavPal Hatsoff to your patience on responding to every question with a very detailed meaningful solution. Such a genius ! You are a "Walking Google in QA"

Hi Shahzil, you can try 2 ways 1. Create commands to run your tests from command line and then put these commands in a file and make it a bat file. So you can click and run it 2. You can use some CI tools like Jenkins and add a job with the commands to run your tests. You can then use Jenkins UI to run the tests OR you can create a custom html webpage using HTML, CSS, and JavaScript

Sownanya here are some points that will help you decide: Both Playwright and Cypress are powerful tools for automated testing, but they have different strengths and use cases. Let's compare them: ### Playwright: - Supports multiple browsers (Chrome, Firefox, WebKit). - Allows concurrent testing on different browser types for comprehensive cross-browser compatibility. - Supports multiple programming languages (JavaScript, Python, C#). - Advanced device emulation for responsive testing. - Network interception for efficient API testing. ### Cypress: - Easy to install and use. - Great documentation and community support. - Fast and reliable performance. - Ideal for simple tests. - Provides screenshots. Which one to choose depends on your specific needs: - If you're just starting and need an easy-to-use solution, Cypress is a good pick. - If you require fast headless browsing and more advanced capabilities, Playwright might be a better fit. Consider your project requirements and priorities when making your decision ..

Thanks for the review

Prashant The best language to use for Playwright will depend on your specific needs and requirements. If you are looking for a language with a large community of developers and a lot of resources available, then Java is a good choice. If you are looking for a lightweight language that is easy to use and that is well-suited for web development, then JavaScript is a good choice. In terms of demand, Java and JavaScript are both popular languages for web development. However, JavaScript is becoming increasingly popular, as it is the language of choice for many modern web frameworks. This means that there is likely to be more demand for Playwright with JavaScript in the future.

@@RaghavPal Thanks Raghav

Most welcome Gaddipati

Hi Rohan Yes, you can generate JSON and XML reports in the file explorer in the Playwright framework using Mocha or any other testing framework. Here's how to do it: Install the mochawesome package to generate HTML reports and the mocha-junit-reporter package to generate JUnit XML reports: npm install --save-dev mochawesome mocha-junit-reporter In your package.json file, add the following scripts: "scripts": { "test": "mocha tests/**/*.spec.js --reporter mochawesome --reporter-options reportDir=reports,reportFilename=report", "test:junit": "mocha tests/**/*.spec.js --reporter mocha-junit-reporter --reporter-options mochaFile=reports/test-results.xml" } Create a reports folder in the root of your project: mkdir reports Run your tests using the npm test command to generate the JSON and HTML reports in the reports folder. The report.json file contains the JSON report and the mochawesome.html file contains the HTML report. Run your tests using the npm run test:junit command to generate the JUnit XML report in the reports folder. The test-results.xml file contains the JUnit XML report. That's it! You can now view your JSON, HTML, and XML reports in the reports folder in your project directory

@@RaghavPal I tried above solution but getting error: 1. Missing script: "test:junit" 2. unknown option '--reporter-output=report/' 3. Could not load reporter "json,html": 4. Playwright Test did not expect test() to be called here.

Rohan It seems like there might be a few issues with the commands you used. Here are some possible solutions: If you are getting the error "Missing script: 'test:junit'", you may need to add a "test:junit" script to your package.json file. You can do this by adding the following line to your "scripts" section: "test:junit": "playwright test --reporter=junit --output=report/results.xml" This script will run Playwright tests with the JUnit reporter and save the results in a file named "results.xml" in the "report" folder. If you are getting the error "unknown option '--reporter-output=report/'", it might be because you used "--reporter-output" instead of "--output" in your command. Try using the following command instead: npx playwright test --reporter=junit --output=report/results.xml This should run the Playwright tests with the JUnit reporter and save the results in a file named "results.xml" in the "report" folder. If you are getting the error "Could not load reporter 'json,html'", it might be because the "json" and "html" reporters are not installed. To install them, run the following command: npm install mocha-multi-reporters --save-dev This should install the "mocha-multi-reporters" package, which includes the "json" and "html" reporters. Then, you can use the following command to run Playwright tests with both the JUnit and HTML reporters: npx playwright test --reporter=mocha-multi-reporters --reporter-options configFile=config/mocha-multi-reporters.json This command uses the "mocha-multi-reporters" package to run Playwright tests with both the JUnit and HTML reporters, as specified in the "config/mocha-multi-reporters.json" file. If you are getting the error "Playwright Test did not expect test() to be called here", it might be because you are using the "test()" function outside of a test file. Make sure that you are calling the "test()" function within a test file, and that the test file is included in your "testMatch" configuration in your "playwright.config.js" file.

@@RaghavPal Thank you so much Raghav...

Hi, Cypress Time-Travel and Playwright Tracer are both tools that allow you to record and replay user interactions in a web application, but they have some differences in how they work and what they offer. Cypress Time-Travel is a feature built into the Cypress end-to-end testing framework, and it allows you to go back in time and replay individual commands to see how they affected the application. This can be useful for debugging tests and understanding how an application works. With Cypress Time-Travel, you can replay commands step by step, examine the state of the application at each step, and see the exact network requests and responses. Playwright Tracer, on the other hand, is a standalone tool for recording and replaying user interactions with a web application. It works by recording the browser's internal trace data, which includes information about the layout, style, and content of the page, as well as network requests and responses. Playwright Tracer allows you to replay the trace data to see how the application behaves, and you can use it to diagnose performance issues and identify bottlenecks in your application. In conclusion, both Cypress Time-Travel and Playwright Tracer can be useful for debugging and understanding how a web application works, but they have different approaches and features. You may find one or the other more suitable for your specific use case depending on your needs

@@RaghavPal Amazing, thanks!!

@@RaghavPal Is that you ChatGPT?

great

Hi Ganesh, You can try using Cypress Studio, which is a visual testing tool that allows users to create tests without writing any code. It works by recording user interactions and generating code based on those interactions. The generated code can then be executed as Cypress tests.

Live now Saurabh

@@RaghavPal Thank you Raghav for quick tutorial ✌👍

Hi Preethi, It would have been useful, if you have given more details like if you like to use manual or automation testing, but in general here are some steps to get started with web application and UI testing: Choose a testing framework: There are several testing frameworks to choose from, such as Selenium, Cypress, or Puppeteer. Choose one that you're comfortable with and that best fits your needs. Check this - ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-afbK2JL45xY.html Get hands-on experience Read documentation and tutorials Continuously practice: As you gain experience, take on more complex projects and continue to expand your knowledge.

Most welcome Amit

Yes, that's correct. Playwright now has a UI Mode that allows you to run and manage your Playwright tests from a graphical user interface. The UI Mode provides a dashboard similar to Cypress Dashboard, where you can see the status of your tests, view logs, and debug test failures.

Yes

Not yet Gourav

@@RaghavPal Do you think Jest is useful for api testing?

Yes Gourav Jest is a powerful option for API testing, offering several advantages and making it a popular choice for developers and testers. Rich mocking capabilities Easy to learn and use Fast and efficient Flexible and extensible Some specific ways Jest can be used for API testing: Testing API endpoints for various HTTP methods (GET, POST, PUT, etc.) Validating response data format and structure Checking for error codes and handling edge cases Mocking API responses for controlled testing scenarios Performing integration tests that involve both your application and the API

Yes, will add a video on this soon

Yes, it's good