ReTest review

ReTest is GUI software test automation, not a general-purpose hosted API or a standalone test library. The vendor describes a product for manual visual difference testing, Selenium test automation and AI-based test automation. Its homepage also lists a testing API and CLI, with both available through GitHub and Maven Central.

In a QA stack, ReTest sits alongside browser-based application tests: teams can use it to inspect visual differences, create and maintain Selenium tests, and focus automation on changes. The vendor also describes visual anomaly detection, data-independent test automation, and cross-browser and cross-device testing. That puts it across both regression review and automated test workflows, rather than limiting it to a single assertion library.

The architecture and current commercial availability need checking before adoption. Current pricing research reports that ReTest has ceased commercial operations. Confirm that the product, API and support are still available before designing a production dependency around them.

The integration surfaces the vendor names are a software testing API and a CLI. The homepage says both are available on GitHub and Maven Central. It does not identify the API protocol, authentication model, request and response formats, or CLI commands, so confirm those details and current documentation before connecting ReTest to a build pipeline.

The vendor's published material names no SDK or supported programming language. Ask ReTest which client libraries and language versions it supports, and whether the API is stable and versioned. Do not assume that a Maven Central listing means a particular Java SDK or a documented integration path; confirm the artifact and its maintenance status.

For testing features, ReTest describes Selenium test creation and maintenance, visual difference filters, anomaly detection and AI-based automation focused on changes. The homepage also claims cross-browser testing. It does not lay out CI integrations, plugins or a supported browser matrix, so verify those against current vendor documentation before committing.

ReTest has no current published plans or billing terms in the available pricing research, so we cannot give a starting price or estimate a production bill. The research also reports that the company has ceased commercial operations. Treat availability and any commercial offer as items to confirm directly before evaluating the tool for a funded project.

There is no listed free plan, free-trial term, or published usage-based rate to compare. The vendor does not publish costs by request volume, seats, browsers, test runs or compute in the available pricing information. That means we cannot calculate how the bill would grow as a test suite expands, or identify overages and add-ons.

Ask for current written terms covering licensing, deployment, usage limits, support and renewal. If ReTest is unavailable commercially, confirm whether the GitHub and Maven Central artifacts can legally and practically be used without a paid service. Do not assume that public access to an artifact means it is free to use or supported.

The homepage points to a testing API and CLI on GitHub and Maven Central, but that alone does not establish that ReTest is open source. The available vendor material does not publish a licence or self-hosting terms. Check the repository licence and the terms for every artifact before shipping it or modifying its source.

ReTest does not publish data-export details in the available material. Ask how test cases, baselines, visual results and configuration can be exported, and whether those formats remain usable outside ReTest. Also confirm whether any part of the workflow depends on a hosted service.

Migration effort will depend on those answers. Selenium tests may offer a familiar automation surface, but visual baselines, filters and AI-based workflows could require replacement or conversion. Before adoption, request an export path and a clear account of dependencies; do not treat GitHub availability as proof of portable data or a self-hostable product.

ReTest describes visual anomaly detection, Selenium automation, cross-browser and cross-device testing, and a testing API and CLI. The available material does not publish API rate limits, test-volume limits, availability commitments, scaling guidance or a supported browser and device matrix. Ask for these details, plus the API's versioning and failure behavior, before making it a required CI step.

The same checks apply to security and compliance: request documentation for authentication, data handling, retention, access controls and any applicable certifications. Confirm where screenshots, test results and application data are processed and stored. The vendor's homepage describes an easy setup and integration, but does not provide operational guarantees.

Commercial continuity is a larger concern than feature fit. Current pricing research reports that ReTest has ceased commercial operations, and no current pricing or support terms are published. Verify that support, updates and the service itself remain available; plan a fallback for regression checks if the dependency becomes unavailable.