Wow, that’s an impressive spreadsheet There are some empty fields, does it mean you need to finish them? (because from my knowledge of Cypress, many of them could have 5s. Also, I thought that iframes testing was actually one of the Cypress weaknesses. Maybe they improved it since then. ). Anyway, it seems that price might be the main decision factor for you. At least, when I was checking TestComplete (as we have been using Swagger by the same company), the price was the main reason why we didn’t go with them. Otherwise, if you use Swagger, Zephyr etc., then TestComplete could be a good combination, I believe.
I would personally try to write a few generic test scenarios in each of the tools (the same scenario in each of them). To see what your team prefers.
For example, I like that Cypress has really good tutorials and a wide community to help. It’s generally very user-friendly. When I started learning it 1 year ago, there was no one around me who would know it; I relied heavily on googling On the other hand, then I saw a video with one automation engineer from a pretty large company. They used Cypress for a few years, then they’ve decided to switch to Playwright. For them, parallel test runs were very important. Also, their QA automation teams were basically QA devs, so they enjoyed the fact that Playwright was designed by devs for devs.
Great blog post! The spreadsheet is also nice and thorough.
I think it’s really interesting that you essentially listed the tools you’re deciding between in order from “least open” to “most open” (with all of the associated pros and cons that come with each of those things).
My 2¢ would be - overall, for an org just getting started with automation, Cypress may be a good “middle of the road” solution balancing the pros and cons of completeness of solution, community, supportability, cost, etc.