metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shane Ardell <>
Subject [DISCUSS] Migrate from Protractor to Cypress
Date Wed, 19 Sep 2018 11:48:59 GMT
Hello everyone,

Currently, we use Protractor to run our UI "end-to-end" tests. However,
there are a handful of major advantages we can gain from switching to

   - As with most Selenium-based e2e testing frameworks, Protractor suffers
   from test flakiness. This is because Selenium runs outside of the browser
   and executes remote commands across the network. To work around this at the
   moment, we are using protractor-flake to re-run failed tests, but this is
   more of a crutch than a fix. Cypress executes in the same run loop as the
   application it's testing, and as a result does not suffer from the same
   - As a result of its architecture, Cypress runs much faster than
   Protractor. This is especially critical if e2e tests are added to the CI
   build in the future.
   - Protractor is incredibly hard to debug. In contrast, Cypress comes
   with a plethora of debugging features, some of which you can see in action

Does anyone else have thoughts or opinions on switching to Cypress or
staying with Protractor?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message