 i made my own because android util mutableboolean is deprecated in p  if you have any ideas for a similarly concise but less ugly way of letting tests know whether the loader decided to request a new seed  umm  i suppose you can subclass callbackhelper and pass whatever data you want from it i tried a few things but i will keep it as is if you do not object  conceptually i want a  future boolean  testloaderresult  object for which i can set the boolean value without unblocking the test thread  in requestseedfromservice and then unblock it later  in onbackgroundworkfinished basing such on object on callbackhelper might not be any better than what i have now  i cannot explicitly protect the derived class  boolean with callbackhelper s internal lock  so the boolean field would need to be handled just as carefully as mutableboolean currently is  basing the object on futuretask is confusing because the runnable callable has nothing to do  i could use completablefuture or blockingqueue  like a go channel  but those makes it difficult to separate setting the boolean from unblocking the test thread 