CloudTest Terminology

Message – Messages are the HTTP requests or XML sent to a web application or web service. Messages are represented visually in CloudTest as boxes in the icon view and URL values in the list view.

Script - CloudTest Scripts are written in JavaScript and allow you to add custom logic to a Test Clip. For example, a script that modifies the input data for a message based upon a set of status codes from the previous message response extracts data or validates responses.

Scope - the ability to set scope on objects in the repository that will define whether an item is private, public, or local. Scope determines whether the information about an item can be accessed from outside of the item. What information that may be depends upon the item.

Chain – A chain is an arbitrary grouping of messages, scripts, or checkpoints within the current Test Clip. This grouping may be used to control the timing of the chain members. Chains are often used in analytics.

Page – A page is a representation of a given HTML page, or URL as represented by its main "HTML Document" and all the resources to which it refers. In CloudTest, a page can retrieve its resources statically (as recorded) or dynamically (as it exists at runtime of the test). Pages have additional load and cache settings as well as override settings at the page, clip, track, and composition level.

Test Clip - The building block of testing in CloudTest is the Test Clip. A Test Clip is a visual script that is composed of a series of timed or sequenced events (an event can be, for example, an HTTP request, a SOAP message or a UI browser action). Once built and debugged, these Test Clips can be reused for any type of testing . . . functional testing, load testing, performance testing and Web UI testing where appropriate.

Composition - A Test Composition is a multi-track interface where test clips can be placed at different times and tracks to create complex testing scenarios. This interface is similar to music and movie digital creation tools. Test Compositions are created by dragging and dropping Test Clips directly onto a timeline or in a sequence based on when they should execute.

Target - A Target points to the application, service, or web site that you want to test, including its location (URL) and any authentication information necessary to successfully run a test. A Target also contains a specification of the information needed to properly format and send messages to the given service or site.

Monitor Server - A Monitor Server defines which hardware resources will be monitored. Typical Monitor Servers are Linux/Windows/Mac, database, and application servers. SNMP devices are also Monitor Servers. A Monitor Server does not define the metrics to be captured; just ‘how’ they will be captured (IP Addresses, ports, authentication, etc.).

Monitor - A Monitor defines the resources for which you will capture data to be used in analytics. This data typically includes statistics on resource usage, processes and activity. Monitored data appears in the Dashboard on the same timeline as test metrics such as response times and error rates. Reference: Monitoring FAQ

Dashboard - A Dashboard is where you view and analyze your test results. CloudTest provides a wide variety of analytic widgets to fill your Dashboards. You can use one or more widgets to track your test in real time and capture results for post-test analysis.

Conductor - CloudTest Conductor is an agent that runs on a client machine. You will need to install a CloudTest Conductor on a machine for any one of the following purposes:

  • To record HTTP/S network traffic.
  • To run Web UI tests in a browser.
  • To monitor machine statistics (CPU usage, for example)

Virtual Users are software programs or services that, when executed iteratively, generate traffic from their location to target servers or services, as would real users of these same servers or services.

Load Testing (also known as Performance Testing) is the use of a coordinated community of virtual users to place “load” on servers or services simulating some future workload for evaluation. Many different categories or terms for performance testing with virtual users are in current use such as benchmarks, endurance, stress tests, blow-up tests, etc.