A session is a medium to send commands to the specific test application; a command is always performed in the context of a session. As we saw in the previous section, a client uses the session identifier as the sessionId parameter before performing any command. The client library requests the server to create a session. The server will then respond with a sessionId endpoint, which is used to send more commands to interact with the application(s) being tested.