Skip to content

Upload Test Reports to rehub

Set Up Local Build

Test reports can be easily uploaded to rehub. For this our existing test case has to be adjusted only slightly. It is possible to upload test reports when we execute the test locally or in a CI/CD environment. For the latter, you can follow this description in order to execute your test with Travis CI.

Remember to set the property for the ChromeDriver executable when you want to execute the test locally (and remove it when you push). If you don't want to change this every time you execute your test locally, you can simply add the chromedriver.exe to your path.

To upload reports you will need a retest account to gain access to rehub. After the initial registration, you will receive a 14-day trial.

The first step is to modify the setUp() method in our existing test case to enable the upload to rehub. There are two ways to achieve this:

  • Set the REHUB_REPORT_UPLOAD_ENABLED_PROPERTY_KEY system property (you have to do this before RecheckImpl is created)
void setUp() {
    System.setProperty( RecheckProperties.REHUB_REPORT_UPLOAD_ENABLED_PROPERTY_KEY, "true" );
    re = new RecheckImpl();
    // ...
  • Set the rehub flag via RecheckOptions
void setUp() {
    RecheckOptions options = RecheckOptions.builder().enableReportUpload().build();
    re = new RecheckImpl( options );
    // ...

If we execute the test locally and the configuration was successful, your browser will pop up and you will be prompted to login. Afterwards, you can find your test reports on rehub dashboard.

Enable rehub Globally

If you have multiple tests and don't want to adapt all of them to upload to rehub, it is easier to set the system property via the mechanism that triggers your tests. Suppose you use Maven and the Surefire or Failsafe plugin for test execution, you can adapt the plugin configuration as follows to enable rehub globally:


Setup Travis CI

After the existing test case has been modified, we may also configure our CI/CD environment. First, set the RECHECK_API_KEY environment variable as shown in the Travis CI documentation.

We need the RECHECK_API_KEY that is generated when the modified test is executed, which you should find in the log. Alternatively, you can invoke Rehub#getRecheckApiKey() locally and the print the returned string to see your personal token.

Travis CI environment variable

Keep your RECHECK_API_KEY token secret!
Anyone with access to your token can add test reports to rehub.
For Travis CI, make sure the Display value in build log toggle is off.

When we have completed all settings and executed the test in our CI/CD environment, we should receive the message Successfully uploaded report to rehub in the Travis CI build log. Now that the test has been executed in the CI/CD environment and the test report has been uploaded to rehub, we can maintain the report in different ways.

Access Your Reports

All your reports can be accessed online. Open rehub, enter your account details, and view/download your reports.

Reports can be opened either with review or recheck.cli. With review, it is also possible to load reports directly from rehub.