retest is Extensible

Every application is different and every environment and organization has special requirements.

We do not want you to make compromises. We want you to be able to extend retest in every aspect to fully reflect all the special requirements and challenges your situation poses.

Therefore, retest has many different configuration parameters (following convention over configuration). Furthermore, in case these not suffice, we are currently working on a public API, which you can implement yourself and extend retest for your needs.

Solving Problems Globally

We believe that problems should be addressed on a global level. So if your application is asynchronous for example, retest automatically waits before every step without you having to tell it explicitly.

The same is true for pretty much everything else. You have a custom component that does special, neat things? You tell retest once and it works everywhere.