I recently added missing close() calls to tests that didn't include them, however, there are cases where a test expects an exception to be thrown and handled by the testng framework or the test could fail for some other reason which would leave a client open as the close() call would be skipped.

We could:

• wrap all close() calls in a finally block.
• use setup and teardown (the names may not be right) to initialize/shutdown the client.