cancel
Showing results for 
Search instead for 
Did you mean: 

JobTestHelper

fbrcls
Champ in-the-making
Champ in-the-making
Hi,

I recently upgraded from version 5.14 to 5.17. I see that the method waitForJobExecutorToProcessAllJobs is moved from TestHelper to JobTestHelper. This method calls the method areJobsAvailable. The implementation of this method was changed from this:

  public static boolean areJobsAvailable(ProcessEngineConfigurationImpl processEngineConfiguration) {
    return !processEngineConfiguration
      .getManagementService()
      .createJobQuery()
      .executable()
      .list()
      .isEmpty();
  }

to this:

  public static boolean areJobsAvailable(ManagementService managementService) {
    return !managementService.createJobQuery().list().isEmpty();
  }

The .executable() was removed. Is there a reason for this? This method returns now "true" if there are timers waiting. It wasn't the case before.

I made my own implementation of this method and putted the .executable() back. But the query always returns an empty list even if I have waiting jobs with retries > 0 and dueDate = null. Is this a bug?

Thanks for your support.
1 REPLY 1

trademak
Star Contributor
Star Contributor
We changed our tests to use the new async executor and the check if jobs are available should not check for executable anymore with the tests logic we have currently.

Best regards,
Getting started

Tags


Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.