Cypress is a widely used, free UI test automation tool for websites. The Cypress approach is code-based and browser-based: Tests are developed, executed, analyzed and updated in the browser using JavaScript.
Cypress shines with its seamless integration into the Chromium dev tools and the "UX time travel" feature, which allows to rewind and fast-forward through a test run recording like a video.
| Cypress | QF-Test | |
|---|---|---|
| Setup and configuration | ||
| Easy setup for non-developers | ❌ | ✅ |
| License | ||
| Open source | ✅ | ❌ |
| Free | ✅ (Commercial add-ons) | ❌ |
| Supported Technologies | ||
Web applications | ✅ | ✅ |
Java applications | ❌ | ✅ |
Windows applications | ❌ | ✅ |
Android applications | ❌ | ✅ |
iOS applications | ❌ | ✅ |
Hybrid applications | ❌ | ✅ |
| Web APIs | ❌ | ✅ |
| PDF documents | ❌ | ✅ |
| Scripting languages | ||
| JavaScript | ✅ | ✅ |
| Groovy | ❌ | ✅ |
| Python | ❌ | ✅ |
| Target Group | ||
| Testers | ❌ | ✅ |
Developers | ✅ | ✅ |
| Platform support | ||
| Cross-platform | ✅ | ✅ |
| Cross-browser | ✅ | ✅ |
| Supported browser drivers | ✅ CDP | ✅ CDP |
| Mobile browsers | ❌ | ✅ |
| Test Development | ||
| Structuring test suites, sets, and cases | ❌ Flat code hierarchy | ✅ Nested tree structure |
| Component identification | ✅ CSS Selectors | ✅ Component nodes |
| Easy component maintenance | ❌ | ✅ Central maintenance |
| Integrated debugger | ❌ | ✅ |
| Test run log | ❌ | ✅ QF-Test run log, HTML Report, XML Report, JUnit Report |
| Multi-tab interface | ❌ | ✅ |
| Comprehensive Documentation | ✅ | ✅ |
| Advanced Features | ||
| Parallelisation | ❌ (Cloud-only) | ✅ |
| Headless testing | ✅ | ✅ |
| Accessibility testing | ❌ | ✅ |
| On-device testing | ❌ | ✅ Android (iOS coming soon) |
| Support and consulting | ||
| Professional support | ❌ | ✅ |
| Training and consulting | ❌ | ✅ |
| Free webinars | ❌ | ✅ |
The tool price is only a small part of the test project costs. The main part is the personnel costs, i.e. the effectiveness with which tests can be implemented and maintained is the most decisive factor. This is not taken into account in the pure tool price consideration. In addition, the test tool pays for itself after approximately 3 test cycles. Further information on testautomation and ROI
1. Functional cookies
We use functional cookies to ensure the basic functionality of the website.
2. Performance and statistic cookies
We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.
This cookie is used to track from which website the anonymized user proceeded to our website.
The Matomo session cookie is used to track the visitor's page requests during the session.
is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).
short lived cookies used to temporarily store data for the visit.
short lived cookies used to temporarily store data for the visit.
