So first of all - we ❤️ Cypress. We are inherently biased to like any company that creates automation tooling and cares about developer happiness. So when we set out to write a tool for developers that enables stability in the Testim enterprise product - building it on top of Cypress was our first go-to strategy.
However, we were completely unable to use Cypress as the basis of our platform and no-longer recommend it to our users for the following reasons.
Cypress builds on the jQuery API which was a very appealing API in the past but it creates a very confusing promise API.
Cypress does not support running test code in multiple tabs. This is a requirement for a lot of our large enterprise customers so we did not expect this to be any different in Testim Code.
Then we will re-consider. Those issues are fundamental in our opinion and are a show stopper.
Updated almost 2 years ago