test_pt_configure_proxy() tests should be improved.
From legacy/trac#9288 (moved):
Could we expand the unit tests so that they actually check the expected outputs? That is, I expect that configuring a proxy is supposed to result in some changes to the proxy, to the or_state_t object, calls to other function, and changes or calls to other stuff. There are lots of bugs that could lurk here that wouldn't get tested if all we check for is "return 0 five times, then return 1."