Unit testing concurrent code

A session at JavaZone 2014

Wednesday 10th September, 2014

1:40pm to 1:50pm (CET)

While software engineers can disagree on almost any concept of programming best-practice, the necessity of writing unit tests remains undisputed. With the advent of concurrent applications and the ongoing deprecation of the one-thread-per-request model, unit tests do however miss an increasing fraction of programing errors such as race conditions or dead-locking code. But is it even possible to write tests that revise such errors? In the end, a good unit test is characterized by a determined execution path what effectively prevents the use of concurrency within a single test. However, there are tools and programming principles that allow for unit tests of concurrent code. This talk reviews typical mistakes made when concurrent code is tested and introduces Thread Weaver, a test suite for writing valid unit tests that uncover concurrency-related programming errors.

About the speaker

This person is speaking at this event.
Rafael Winterhalter

software consultant who likes static types

Coverage of this session

Sign in to add slides, notes or videos to this session

JavaZone 2014

Norway Norway, Oslo

9th11th September 2014

Tell your friends!


Time 1:40pm1:50pm CET

Date Wed 10th September 2014

Short URL


Official event site


View the schedule


See something wrong?

Report an issue with this session