Test missing custom variable behaviour

With current implementation, this test fails because missing environment
variables aren't set.

I don't think this is ideal behaviour (I think if you say `d12f("FOO")`
it's reasonable to expect the presence of `settings.FOO`) - I want to
think about it more before it goes into mainline. I can see the sense
behind both.