Transcripted Summary
Let's kick off with our first question - what exactly is Cypress?
In simple terms, Cypress is your go-to tool for testing anything that operates within a browser.
It provides the flexibility to write various types of tests - including component, end-to-end and API tests.
What sets Cypress apart is its ability to function directly within the browser, meaning it allows us to test our application right where they intend it to operate.
So how does it work?
Cypress operates by creating two iframes.
One of them runs our application, and the other one runs the Cypress script.
This setup enables Cypress to interact directly with our application, eliminating any need for a middleware.
That's a significant distinction from tools like Playwright or Selenium.
Unlike these tools, Cypress doesn't really rely on a web driver.
It doesn't aim to automate the browser, but focuses more on automation of the app.
Cypress is a testing tool created for developers.
But thanks to its simplicity, many testers have also fallen in love with it.
However, it's worth remembering that Cypress' main function is testing.
While it works brilliantly with app development and testing, it might not be an optimal choice for tasks like web scraping or scripting for other websites.
Cypress introduces an innovative approach to testing.
It's worth delving into its philosophy and to understand why it has certain limitations, such as the lack of a hover command or support for multiple browser tabs, and its limited compatibility with various browsers.
I like to say that it brought testers closer to web development, and developers closer to testing.
Cypress will nudge you towards an understanding of the web, and I believe that's one significant advantage that Cypress offers.
