This page is used to list all the important terms ATS uses when it comes to performance testing

---

Loader

An ATS Agent instance used for running performance actions. It is usually located on some remote host i.e. not Test Executor or Tested Application hosts

---

Users

The threading pattern defines how many users will run the actions. The meaning is the same as the real users (or customers) of your Test Application in its real life.

Note that we sometimes say threads instead of users and this is OK, because we use a Java thread for doing the job of a test scenario user.

---

Action

This is single step that the user can run in a performance test. It is defined into a Java method which lives at the remote Loader.

---

Action queue

Also call performance queue. It is an ordered list of actions as defined in the scenario

---

Iteration

One execution of an action queue.

The threading patters define how many times an iteration is executed.

You cannot executed just a single action. You can executed an iteration of an action queue which consists of one or many actions.

---

Action response

The time it took (in ms) for the execution of an action

---

Action transfer rate

There is a way to measure how much data was transferring data over the wire by some special action

---

Agent component

All actions are packaged into some jar(s) which are called Agent components.

The framework itself uses Agent components when need to run some code on a remote host - for example there is an action class used for running file system operations on a remote host.

---

Back to parent page

Go to Table of Contents

---