SaaS Ranking

Transparency alternatives to PractiTest

Other Test automation vendors we measure, sorted by how much we found at them and not at PractiTest. This is a comparison of disclosure, not of features or fitness.

12 shown of 44 that differ from PractiTest on at least one criterion we measured for both. Public transparency score, not a product or security rating.

PractiTest has 7 gaps in what we could measure: Data processing agreement, Data location stated, Status page with history, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at PractiTest” is the one that closes them.

VendorScoreFound there, not found at PractiTestFound at PractiTest, not found there
Replicated Compatibility Matrixreplicated.comSee also Transparency alternatives to Replicated Compatibility Matrix 52/100 5 Data location stated, Status page with history, HTTPS enforced with HSTS, +2 3 Subprocessor list, Uptime SLA with a figure, Notice before subprocessors change Compare
Katalonkatalon.comSee also Transparency alternatives to Katalon 48/100 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 3 Subprocessor list, Uptime SLA with a figure, Notice before subprocessors change Compare
Testsigmatestsigma.comSee also Transparency alternatives to Testsigma 48/100 4 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +1 3 Subprocessor list, Public pricing, Uptime SLA with a figure Compare
Rainforest QArainforestqa.comSee also Transparency alternatives to Rainforest QA 39/100 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 4 Subprocessor list, Public pricing, Uptime SLA with a figure, +1 Compare
Cypresscypress.ioSee also Transparency alternatives to Cypress 65/100 3 Data location stated, Status page with history, HTTPS enforced with HSTS 1 Uptime SLA with a figure Compare
Applitoolsapplitools.comSee also Transparency alternatives to Applitools 43/100 3 Data processing agreement, Status page with history, Named privacy contact 2 Subprocessor list, Notice before subprocessors change Compare
ACCELQaccelq.comSee also Transparency alternatives to ACCELQ 39/100 3 Data processing agreement, HTTPS enforced with HSTS, Named privacy contact 3 Subprocessor list, Public pricing, Uptime SLA with a figure Compare
Global App Testingglobalapptesting.comSee also Transparency alternatives to Global App Testing 39/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
Horizonthetestmart.comSee also Transparency alternatives to Horizon 39/100 3 Data processing agreement, HTTPS enforced with HSTS, Named privacy contact 3 Subprocessor list, Public pricing, Uptime SLA with a figure Compare
Functionizefunctionize.comSee also Transparency alternatives to Functionize 35/100 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact 4 Subprocessor list, Certifications named, Uptime SLA with a figure, +1 Compare
Allure TestOpsqameta.ioSee also Transparency alternatives to Allure TestOps 30/100 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact 3 Subprocessor list, Uptime SLA with a figure, Notice before subprocessors change Compare
Applauseapplause.comSee also Transparency alternatives to Applause 26/100 3 HTTPS enforced with HSTS, No third-party tracking before consent, Named privacy contact 4 Subprocessor list, Public pricing, Uptime SLA with a figure, +1 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.