https://cypress.io logo
Selecting Cypress for Functional Testing
# i-need-help
c
Hi, I am evaluating Cypress as an alternate to Selenium, or Playwright. Most examples i see use Cypress as a Testing framework for testing a local application, and not something similar to Selenium, where all URLs are in a remote domain. Is Cypress meant to be a replacement for Selenium, or is only to be used as an Integration Testing Framework, where the target application must be available locally, and Cypress Tests The ( let's say ) React Internals, and not much suited for Functional Testing of WebApplication or WebSites?
w
There doesn't have to be a locally running application. If you install Cypress and set up e2e tests, for example, you will get a lot of example tests showing how to use it, all of them test a remote url (https://example.cypress.io/). It's still really common to have tests visit a local application because it lets you test new builds of that application without having to deploy it to a remote environment. But that depends on how your company works. Plenty of people write Cypress tests that target QA or Staging environments for example. The only difference is in what URL you tell Cypress to visit, Cypress doesn't care if it's local or remote as long as it serves a web page 🙂
2 Views