Can Cypress be used for performance testing? If so, what are the limitations and best practices for measuring and optimizing application performance using Cypress?
What technology expertise is required for cypress ?
How can we multiple URL navigation Cypress handle origin issues? able to navigate to the second URL, but on the third URL, it’s failing.
Playwright supports multiple programming languages like JavaScript, TypeScript, Python, and C#. Currently, Cypress primarily supports JavaScript. Are there plans to expand Cypress’s language support,?
What is fixtures in Cypress. How are fixtures useful in testing? Cab you please elaborate on the same
How does Cypress compare to Playwright in terms of test execution speed, especially in scenarios involving complex, modern web applications?
How to create a good framework in Cypress?
What is the best alternative to using cy.wait (xxxx)? I would like for Cypress to wait for an element to become available rather than a static wait time.
How does Cypress’s architecture and approach differ from traditional Selenium WebDriver, and in what scenarios would you choose one over the other?
Playwright vs Selenium
How much coding knowledge requests to use Cypress?
Prerequisite to learning Cypress
Where do we place our element locators if we have to test the same login testcase with valid, invalid and empty data?
Being a Cypress tester i belive that even though the Cypress XPath plugin is deprecated, Cypress still offers a powerful way to handle complex locators using CSS selectors. CSS selectors are generally more efficient in Cypress due to their native support and speed in browser DOM traversal.
For complex cases where XPath might have been your go-to, consider refactoring your selectors to utilize CSS. If you’re deeply reliant on XPath, a workaround would be to use a custom function to parse XPath into equivalent CSS. I’ve found that embracing CSS selectors simplifies test maintenance and improves test run times significantly.
Hope this helped 
Hey there!
From what I grasped from the session, Anna emphasized a few key practices: start simply by focusing on clear and descriptive test names, utilize beforeEach hooks to set up initial states, and avoid hardcoding values. Instead, use Cypress fixtures for external data and reusable commands for repetitive steps. This approach not only keeps tests clean but also prevents duplication and enhances readability.
Hope this helped
Hello there!
From the session what i recall is that Anna highlighted that Cypress is a modern JavaScript-based testing framework specifically designed for end-to-end testing of web applications. Its suitability stems from its fast, real-time reloading, automatic waiting, and easy setup. It offers an all-in-one testing framework that’s accessible directly from the browser, enabling developers and testers to write and debug tests more efficiently.
Hope this helps
Hey there!
From my experience in Cypress automation, I say that for beginners, start with a simple structure. Place your test files under the cypress/integration folder, and name your test cases clearly. Anna demonstrated a basic example where she used to describe, and it blocks to structure the test logically, including assertions like cy.get() and cy.contains(). She suggested keeping your tests isolated and modular by organizing them around specific features or components.
Hope this helped
Hello there!
From my experience, while transitioning from manual to automated testing can be daunting. The primary challenge is grasping the coding aspect and changing the mindset from exploratory to structured scripting. She suggested starting with Cypress’s documentation and practicing writing small scripts to get comfortable. Overcoming the initial learning curve can be facilitated by pair programming or mentorship, which provides hands-on guidance.
Hope this helped
Hello there
From what I grasped from Anna’s session, she pointed out that Cypress is often favored for its robust documentation, strong community support, and user-friendly interface, making it ideal for projects where rapid test development and debugging are priorities. On the other hand, Playwright is selected for its multi-browser support and ability to handle scenarios like cross-browser testing. The decision usually hinges on project requirements—if you need more comprehensive browser coverage, Playwright might be the better choice.
Hope this helped
Hello there!
As a tester, handling iframes, multi-tab scenarios, and cross-origin requests are some of the common challenges faced by Cypress. While Cypress provides workarounds, understanding these limitations early on can save time. Using Cypress’s extensive documentation and GitHub issues can also provide valuable community-driven solutions.
Hope this helped