Unit test succeeds in debug mode but fails when running it normally

The reason is almost certainly that your breakpoint in the debugger is halting the main thread but not any of the background threads - the ones in the ExecutorService. When debugging in eclipse you can change the breakpoint to halt all threads instead of just the main one.

When not debugging the submission of the task and the immediate cancellation are so quick that you are cancelling the task before it even runs once. Try adding a sleep delay between these lines:

final Future<String> future =  pool.submit(new TaskChecksForInterruptedBit());Thread.sleep(1000);final boolean wasJustCancelled = future.cancel(true);

You have to make sure your task actually started running. It may get cancelled before it even has a chance.

public class ExecutorServiceTest {    private int numThreads;    private ExecutorService pool;    private volatile boolean interruptedBitSet;    private static final CountDownLatch latch = new CountDownLatch(1);    @Before    public void setUp() {        numThreads = 5;        pool = Executors.newFixedThreadPool(numThreads);    }    class TaskChecksForInterruptedBit implements Callable<String> {        @Override        public String call() throws Exception {            interruptedBitSet = false;            latch.countDown();            while (!Thread.currentThread().isInterrupted()) {                System.out.println(System.currentTimeMillis());            }            System.out.println("haha");            interruptedBitSet = Thread.currentThread().isInterrupted();            return "blah";        }    }    @Test    public void testCancelSetsInterruptedBitInCallable() throws Exception {        final Future<String> future =                pool.submit(new TaskChecksForInterruptedBit());        interruptedBitSet = false;        latch.await();        final boolean wasJustCancelled = future.cancel(true);        Assert.assertTrue(wasJustCancelled);        // Give time for the thread to notice the interrupted bit and set the flag        Thread.sleep(5000);        // This succeeds when stepping through w/ a debugger, but fails when running        // the test straight. WHY?        Assert.assertTrue(interruptedBitSet);        Assert.assertTrue(future.isDone());        Assert.assertTrue(future.isCancelled());    }}

I know this is old but I just had the same problem.My issue was that I had an IEnumerable that I was enumerating and checking the output.

When running the Unit test, the IEnumerable was returning a different ordering that when debugging. This is the nature of IEnumerable and simply adding an OrderBy clause solved my problem.

I hope this helps someone out there as it can be a frustrating problem to find.