Basic smart-proxy crud tests

Is the reason for this call to potentially raise an exception due to the the new ``default_url_on_new_port`` method? For what is worth, all other CLI tests will return an error attribute that can then be checked via assertion, so this is a bit different from what we current have...