Ways of Using recheck-web

There are several ways to use recheck-web. If you only want to use recheck-web's capabilities to do difference testing with explicit checks, then you don't have to switch your WebDriver at all; simply add Recheck re = new RecheckImpl() to your test.

If you want to leverage "Unbreakable Selenium", you have to use UnbreakableDriver as a driver wrapper and switch to RecheckWebImpl.

If you want to trigger checks after each GUI action implicitly, you can use AutocheckingRecheckDriver and omit using a Recheck instance.

Similar to the NamingStrategy in recheck, where you can change the enire name of your test reports, you can change the check name in recheck-web via AutocheckingCheckNamingStrategy. The default is the CounterCheckNamingStrategy, but you can also use the ActionbasedCheckNamingStrategy (or implement your own AutocheckingCheckNamingStrategy) and pass is to RecheckWebImpl via RecheckWebOptions:

RecheckWebOptions options = RecheckWebOptions.builder()
                .checkNamingStrategy( new ActionbasedCheckNamingStrategy() )
Recheck re = new RecheckWebImpl( options );

RecheckDriver combines all recheck-web features. Use this class if you automatically want to incorporate new features without changing your recheck-web driver implementation manually.

To summarize:

WebDriver Checks Recheck
Ordinary driver (e.g. ChromeDriver) Explicit RecheckImpl
UnbreakableDriver Explicit RecheckWebImpl
AutocheckingRecheckDriver Implicit Integrated (i.e. not needed)
RecheckDriver Implicit Integrated (i.e. not needed)

For further information you can check out the Javadoc of the corresponding classes and refer to our integration tests, which demonstrate the usage.