DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • What Actually Breaks During Large-Scale S/4HANA Conversions (And How to Prevent It)
  • Comparison of Various AI Code Generation Tools
  • Database Integration Tests With Spring Boot and Testcontainers
  • 7 Awesome Libraries for Java Unit and Integration Testing

Trending

  • Idempotency Under Concurrency: Why Your Application Check Isn't the Last Line of Defense
  • Beyond Manual Mapping: AI-Orchestrated Governance for Hybrid Cloud
  • You Do Not Need a PhD to Become an AI Engineer: The Essential Skill Stack
  • Top Gen AI Frameworks for Go in 2026: A Hands-On Comparison

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Deployment
  4. Five Ways of Synchronising Multithreaded Integration Tests

Five Ways of Synchronising Multithreaded Integration Tests

By 
Roger Hughes
·
Oct. 11, 22 · Interview
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
9.7K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

A few weeks ago I wrote a blog on synchronizing multithreaded integration tests, which was republished on DZone Javalobby from where it received a comment from Robert Saulnier who quite rightly pointed out that you can also use join() to synchronize a worker thread and its unit tests. This got me thinking, just how many ways can you synchronise multi-threaded integration tests? So, I started counting... and came up with:

  1. Using a random delay.
  2. Adding a CountDownLatch
  3. Thread.join()
  4. Acquiring a Semaphore
  5. With a Future and ExecutorService


Now, I’m not going to explain all the following in great detail, I’ll let the code speak for itself, except to say that all the code samples do roughly the same thing: the unit test creates a ThreadWrapper instance and then calls its doWork() method (or call() in the case of the Future). The unit test’s main thread then waits for the worker thread to complete before asserting that the test has passed.


For the sample code demonstrating points 1 and 2 take a look at my original blog on Synchronizing Multithreaded Integration Tests, though I wouldn’t recommend point 1: using a random delay.



Thread.join()


public class ThreadWrapper {



   private Thread thread;



   /**

   * Start the thread running so that it does some work.

   */

   public void doWork() {



   thread = new Thread() {



   /**

   * Run method adding data to a fictitious database

   */

   @Override

   public void run() {



   System.out.println("Start of the thread");

   addDataToDB();

   System.out.println("End of the thread method");

   }



   private void addDataToDB() {



   try {

   Thread.sleep(4000);

   } catch (InterruptedException e) {

   e.printStackTrace();

   }

   }

   };



   thread.start();

   System.out.println("Off and running...");

   }



   /**

   * Synchronization method.

   */

   public void join() {



   try {

   thread.join();

   } catch (InterruptedException ex) {

   Thread.currentThread().interrupt();

   }

   }

 }



public class ThreadWrapperTest {



   @Test

   public void testDoWork() throws InterruptedException {



   ThreadWrapper instance = new ThreadWrapper();



   instance.doWork();

   instance.join();



   boolean result = getResultFromDatabase();

   assertTrue(result);

   }



   /**

   * Dummy database method - just return true

   */

   private boolean getResultFromDatabase() {

   return true;

   }

 }



Acquiring a Semaphore


public class ThreadWrapper {



   /**

   * Start the thread running so that it does some work.

   */

   public void doWork() {

   doWork(null);

   }



   @VisibleForTesting

   void doWork(final Semaphore semaphore) {



   Thread thread = new Thread() {



   /**

   * Run method adding data to a fictitious database

   */

   @Override

   public void run() {



   System.out.println("Start of the thread");

   addDataToDB();

   System.out.println("End of the thread method");

   semaphore.release();

   }



   private void addDataToDB() {



   try {

   Thread.sleep(4000);

   } catch (InterruptedException e) {

   e.printStackTrace();

   }

   }

   };



   aquire(semaphore);

   thread.start();

   System.out.println("Off and running...");

   }



   private void aquire(Semaphore semaphore) {

   try {

   semaphore.acquire();

   } catch (InterruptedException e) {

   e.printStackTrace();

   }

   }

 }



public class ThreadWrapperTest {



   @Test

   public void testDoWork() throws InterruptedException {



   ThreadWrapper instance = new ThreadWrapper();



   Semaphore semaphore = new Semaphore(1);

   instance.doWork(semaphore);

   semaphore.acquire();



   boolean result = getResultFromDatabase();

   assertTrue(result);

   }



   /**

   * Dummy database method - just return true

   */

   private boolean getResultFromDatabase() {

   return true;

   }

 }



With a Future


public class ThreadWrapper implements Callable<Boolean> {



   @Override

   public Boolean call() throws Exception {

   System.out.println("Start of the thread");

   Boolean added = addDataToDB();

   System.out.println("End of the thread method");

   return added;

   }



   /**

   * Add to the DB and return true if added okay

   */

   private Boolean addDataToDB() {



   try {

   Thread.sleep(4000);

   } catch (InterruptedException e) {

   e.printStackTrace();

   }

   return Boolean.valueOf(true);

   }

 }



public class ThreadWrapperTest {



   @Test

   public void testCall() throws ExecutionException, InterruptedException {



   ThreadWrapper instance = new ThreadWrapper();



   ExecutorService executorService = Executors.newFixedThreadPool(1);



   Future<Boolean> future = executorService.submit(instance);



   Boolean result = future.get();



   assertTrue(result);

   }

 }


Having listed all these methods, the next thing to consider is which one is the best? In asking that question you have to define the word “best” in terms of best for what? Best for simplicity? Maintainability? Speed or code size? After all Programming the Art of Making the Right Decision. You may have guessed that I don’t like the random delay idea and prefer the use of a CountDownLatch. Thread.join() is a bit old school; remember that the likes of Semaphore and CountDownLatch were written to improve on the original Java threading techniques. ExecutorService seems a little heavy weight for what we need here. At the end of the day the choice of technique really comes down to personal preference.


Finally, I’ve listed five ways of synchronizing multi-threaded integration tests; however, if you can think of any others please let me know...



The source code for this blog is available on Github.

unit test Integration

Published at DZone with permission of Roger Hughes. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • What Actually Breaks During Large-Scale S/4HANA Conversions (And How to Prevent It)
  • Comparison of Various AI Code Generation Tools
  • Database Integration Tests With Spring Boot and Testcontainers
  • 7 Awesome Libraries for Java Unit and Integration Testing

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook