2

I'm putting together a proof on concept for my team to make the move from Selenium over to Cypress to do E2E testing. We have front end and back end both in different repos and are deployed and released independently. I am trying to figure out where to install Cypress and what the limitations may be depending on my choice.

Option 1: Install Cypress in the front end repo where I can run the tests against a local build and have the tests run as part of the build.

Option 2: Install Cypress in it's own repo and 'visit' the QA environments URL.

Option 2 would be the preferred method as it wouldn't require code changes from the QA analysts going into the source code repo.

If I go with option 2, what are some the benefits that I'd lose from installing Cypress within the source codes repo?

Thanks

I have watched some videos and followed some tutorials on how to implement Cypress E2E tests and I've noticed that they all show to install in the same repo as the source code, but the topic isn't heavily covered. The tutorials just assume that the tests are being written by a developer as opposed to a QA analyst that has limitations in committing code to the src repo.

Joe Hale
  • 21
  • 2
  • If you are going with Option 2 and are using circleci, here is an easy to use utility for trigger your cypress tests from your app repo. https://github.com/bahmutov/trigger-circleci-pipeline – jjhelguero Feb 28 '23 at 15:32
  • Option 1 seems to be the natural choice, since Cypress is essentially white-box testing. As such, the developers would write the tests together with the code. Your QA engineer should team up with the devs. Otherwise, maybe Cypress is not the best choice. And I can second that there is not much documentation about this, not even on the official website. – Marcel Mar 03 '23 at 07:30

0 Answers0