HTTP and HTTPS life cycles are handled identically by CloudTest. Connections are scoped to the Clip level. When the Clip or Clip Iteration ends, all connections are closed.
If a test composition uses nested Clips, and has Merge Targets enabled, then connections are scoped to the parent Clip. For more information about nested clips and Merge Targets enabled, see Nested Clip Properties.
Within a Clip instance, CloudTest opens a connection the first time it plays a Message for a given Target. Then, if you have multiple Targets for the same server, CloudTest will use separate connections.
In "ordinary" sequential playback, CloudTest never opens more than 1 connection.
If Pages are in use, then CloudTest will open additional connections as needed to support parallelism, up to the max defined in the Target settings. The default is 6, which we believe matches modern browsers.
The total number of connections limit used by a Page can be set in the Target Editor—regardless of how many hosts there are—via the target's Connection Options section, using the "Maximum Connections per Host" and "Maximum Total Connections" settings.
The default is no total limit, only the per-host limit.