Thanks for catching this. I believe the idea was that the process would be signaled from the jBPM console instead of being completed automatically by the handler. We should be able to signal the process from the test through the task server to accomplish the same thing, however. David should be able to provide a bit more context on why this changed.
I chatted with David about this today and it appears to be a test issue only. The test is not communicating with the task server to complete task items. He's going to have a look right after he fixes another blocker issue for our 0.3 release this week.
That makes sense that it is a test only issue. Thanks.