testdriver:client

To initialize the TestDriver SDK client, instantiate it with an API key and optional settings. The client automatically reads the TD_API_KEY from the environment or a .env file, applying sensible defaults to streamline setup.

Connect to a sandbox to obtain an active session by authenticating with your loaded API key. Once the TestDriver client is initialized, use the connect workflow to bootstrap the sandbox environment required before running tests.

Yes, you can configure logging and inspect instance and session details. During initialization and after connecting to a sandbox, the TestDriver client exposes settings to manage logging levels and review active session information.

Disconnect gracefully from a TestDriver sandbox after tests by utilizing the client's disconnect workflow. This ensures the active session is properly closed and the sandbox environment is cleanly managed at the end of execution.

No, you do not need an explicit API key to start the TestDriver client. It supports environment-based authentication, automatically reading TD_API_KEY from your system environment or a local .env file to simplify instantiation.