The following terms are commonly used when working with ASM/LTP.

Check: a check evaluates a single transaction such as the availability of a URL, port, or a single run of a Scenario for Selenium IDE or ZebraTester. Sometimes referred to by some of our customers as beacons, monitors.

Script:  Instructions for an automated test tool (e.g. Zebratester, ProxySniffer, Selenium). One Test Case is often represented by one script

Scenario: hypothetical stories to help the tester work through a complex problem or test system

Selenium: a portable software-testing framework for web applications. Selenium provides a record/playback tool for authoring tests without the need to learn a test scripting language

NFR: stands for "Non Functional Requirements"

Test Case: a chain of one or more user steps. Also known as "User Journey"

User Steps: a user interaction with an application

VU: Virtual User which executes the steps in the test script

TT: Think Time, a variable used in test tools to represent the time the user spends between each interaction

Apica Products

ASM: stands for "Apica Synthetic Monitoring". Furthermore, "ASM portal" refers to wpm.apicasystem.com

LTP: stands for "Load Test Portal". Refers to loadtest.apicasystem.com 

ZebraTester: Java based load testing tool developed, maintained, and own by Apica. Apica ProxySniffer is used both for load test scripting as well as for load generation

Types of Private Agents

Private Agent: agent installed on our usual public network agent but reserved for the exclusive use of a specific customer

Public Agent: an agent installed on one of our usual public network agents but available for all customers

OnPrem Agent: an agent hosted by the customer on their own machines; it has the entire Apica infrastructure installed

Types of Load Tests

Scalability Test: a test that quickly locates bottlenecks in the system and to determine the maximum throughput of the system

Concurrency Test: a test that determines the maximum number of simultaneous users and connections in the system

Mixed Test: same as Concurrency Test but only that multiple scenarios are run in parallel with a weighted amount of users in case to generate a more realistic load towards the application

Stability Test: a test that asses the application and system performance stability under sustained load (normally 6-8 hours duration)

Stress Test: a performance test where the level of load is increased over the expected load in production

Disaster Recovery Test: same methodology as Mixed concurrency; however, a Disaster Recovery Test aims to assess how a system behaves during disaster recovery situations such as restart during load, failover recovery after overload outage, etc.