Setting Scope on Targets in Test Clips

Every item has scope. Targets are a special case, they can only be public or local; they cannot be private, because Targets need to be accessed by the Messages or Browser Actions in the Test Clip. Scope for the targets in a test clip can be viewed and set in the Included Targets list of the Clip Editor.



Setting an item’s scope as restrictively as possible allows CloudTest to make memory optimizations during runtime by throwing away unnecessary information.

For example, if a Message is “private”, then its response will not be accessed by another item in the Composition, and therefore we don’t have to save it and can throw away the response as soon as we receive it. Therefore, for efficiency, the scope should be set to “private” whenever possible, and set to “local” or “public” only if it really needs to be. That is why we make everything “private” by default (except for Targets, which are “local” by default since they can’t be “private”).