Alternatives to PractiTest
Other Test automation vendors we measure, sorted by how much they publish that PractiTest does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from PractiTest on at least one criterion we measured for both. Public transparency score, not a product or security rating.
PractiTest has 6 gaps in what we could measure: Data processing agreement, Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “publishes and PractiTest does not” is the one that closes them.
| Vendor | Score | Publishes, and PractiTest does not | PractiTest publishes, and they do not | |
|---|---|---|---|---|
| Applauseapplause.com | 39/100 | 4 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | 5 Subprocessor list, Status page with history, Public pricing, +2 | Compare |
| BrowserStackbrowserstack.com | 63/100 | 3 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent | 2 Subprocessor list, Uptime SLA with a figure | Compare |
| Katalonkatalon.com | 48/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 3 Subprocessor list, Uptime SLA with a figure, Notice before subprocessors change | Compare |
| ACCELQaccelq.com | 39/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Named privacy contact | 4 Subprocessor list, Status page with history, Public pricing, +1 | Compare |
| Global App Testingglobalapptesting.com | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 4 Subprocessor list, Status page with history, Uptime SLA with a figure, +1 | Compare |
| Rainforest QArainforestqa.com | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 4 Subprocessor list, Public pricing, Uptime SLA with a figure, +1 | Compare |
| Xraygetxray.app | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 5 Status page with history, Public pricing, Certifications named, +2 | Compare |
| Allure TestOpsqameta.io | 30/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 4 Subprocessor list, Status page with history, Uptime SLA with a figure, +1 | Compare |
| Ranorexranorex.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 6 Subprocessor list, Status page with history, Public pricing, +3 | Compare |
| Cypresscypress.io | 65/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 Uptime SLA with a figure | Compare |
| Endtestendtest.io | 48/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Status page with history, Uptime SLA with a figure, Notice before subprocessors change | Compare |
| Applitoolsapplitools.com | 43/100 | 2 Data processing agreement, Named privacy contact | 2 Subprocessor list, Notice before subprocessors change | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.