@Paul Bush One of the main advantages of using DI is to allow testing without hard dependencies. You have full control to mock dependencies and test your function code directly.
But it is still possible to test the configure code by setting up the webjobs container as shown in this blog. The idea here being you setup the underlying webjobs context while is the core of how Functions work.
Another approach would of course just involve starting up the local function host and test your functions by directly triggering the function via HTTP or the Admin API for Non-HTTP Functions.