A B C D E F G H I J K L M N O P Q R S T U V W X Y Z agent A program that automatically performs a specific service, such as data collection, without user intervention or on a regular schedule. AC See Agent Controller. Agent Controller A daemon process that resides on each deployment host and provides the mechanism by which client applications either launch new host processes or attach to agents that coexist within existing processes on the host. IAC See Integrated Agent Controller. Integrated Agent Controller A type of Agent Controller for collecting data on local systems only. It is hosted in-process within the Eclipse workbench process. base time The time spent executing a particular method. Base time does not include time spent in other Java methods that this method calls. bottleneck A place in the system where contention for a resource is affecting performance. boundary class In performance profiling, a class that is normally excluded in the filtering criteria, but which is directly invoked by the classes that are included as filters. call stack A list of data elements that is constructed and maintained by the by the Java Virtual Machine (JVM) for a program to successfully call and return from a method. class statistics Statistical information that includes information such as the number of instances of the class in the application, the CPU time spent in that class, the number of calls made to the class, and so on. clock time The elapsed time in real time. Clock time differs from CPU time as thread switches and process context switches introduce uncertainty in performance calculation; clock time does not account for this execution behavior. cumulative time The time that a method spends on the execution stack, including both time spent in the method itself and in other methods that it calls. distributed trace Collected data that describes interactions in a distributed application execution. FFDC See First-Failure Data Capture. First-Failure Data Capture A problem diagnosis aid that identifies errors, gathers and logs information about these errors, and returns control to the affected run-time software. garbage collection Part of a language's run-time system or an add-on library that automatically determines the memory that a program no longer uses, and recycles it for other use. Garbage collection may be assisted by the compiler, the hardware, the operating system, or any combination of the three. host In performance profiling, a machine that owns processes that are being profiled. host process In the profiling tools, an element of the application under test that can leverage the Agent Architecture to externalize application behavior. TPTP See Test and Performance Tools Platform. Test and Performance Tools Platform TPTP originated from and extends the Eclipse Hyades Tools Project, an integrated test, trace, and monitoring environment. Agent Architecture A mechanism for collecting data that can be used by third-party tools on the development platform. Agent Architecture consists of several components such as the Java Profiling Agent and the Default Logging Agent which can be plugged into the overall deployment architecture. instance statistics Statistical information that includes information about an application such as instances of different classes and their size, the packages to which the classes belong, the CPU time spent in an instance of a class, and so on. J2RP See J2EE Request Profiler. J2EE Request Profiler The name of an agent that is attached to the application server process for the purpose of collecting data on the interception points of the application's requests. launch configuration A mechanism for defining and saving different workbench configurations that can be launched separately. Configurable options include run and debug settings. log correlation Correlation is the process of analyzing and determining a set of related events, based on a set of rules that are used to interpret the data contained in the events. Log correction Correlation correlates information within a log file from a single application or across multiple log files generated by different applications. probe Probes are reusable Java code fragments that you write to collect detailed runtime information about a program's objects, instance variables, arguments, and exceptions. logging agent An agent that programmers can create in order to write data (for example Java primitives, objects, or predefined logging structures) to one or more output sources (for example text or XML), for an application under test. logging factory A singleton factory that is used to create, store, and destroy logging agents for public access. logging level In the logging tools, the indicator of the amount of logging to be done. The higher the level, the more information to be logged. LTA See Log and Trace Analyzer. Log and Trace Analyzer A tool that enables developers to view and analyze application log files and XML log files, and to edit symptom database files. log record An entry in a log view that consists of properties and their values. A log record does not contain instances of other log records but has nested levels of entries or children. memory leak The effect of a program that maintains references to objects that are no longer required and therefore need to be reclaimed. method statistics Information about a method that includes the package (and class) to which the method belongs, the number of calls made to the method, the CPU time spent in the method, and the cumulative time spent in that method. monitor In performance profiling, to collect data about an application from the running agents that are associated with that application. package statistics Statistical details about a profiled application that are grouped by package. See also instance statistics. process object The logical representation of a Java process. A process object is identified both by name and a Process IDentifier (PID), and appears in the Monitors view along with the associated agents whenever a Java process is launched or attached to. profiling The process of analyzing the performance, resource utilization, or execution of an application. profiling agent An agent that does a performance analysis of, and profiles an application. profiling filter A mechanism for specifying which information about an application will be analyzed. root node In a graphical representation of data as a tree, a node that has no parents but typically has children. singleton A class that can be instantiated only once. A singleton class cannot be an interface. solution In the symptom database that is used to analyze application logs, information about why an error might have occurred and how to recover from it. stack frame A section of the stack that contains the local variables, arguments, and register contents for an individual routine, as well as a pointer to the previous stack frame. symptom In the Log and Trace Analyzer, an error message. A symptom can have a solution associated with it in the symptom database. Symptom Database An XML file of symptoms including one or more string match patterns with one or more associated solutions that is used in the analysis of event and error messages that occur in an application log. log file In the Log and Trace Analyzer, a file that is generated by an external application which may include application execution information such as error and information messages. XMI model A context-sensitive model that various views can load, and analyze. XMI models are the primary entities that are persisted as a result of profiling or logging an application. XML log file A log file in XML format that is created by a logging agent and used to record plug-in loading events and information. Common Base Event The Common Base Event specification prescribes a common format for logging, management, problem determination, and autonomic computing. It provides a consistent format that facilitates intercommunication between tools that support these goals. Common Base Event objects allow you to develop a common prescriptive event in a consistent format so that tools can be developed to support these goals. http://www.eclipse.org/tptp/platform/documents/resources/cbe101spec/CommonBaseEvent_SituationData_V1.0.1.pdf GLA See Generic Log Adapter. Generic Log Adapter The Generic Log Adapter is a tool that allows you to process application log files and transform their contents into the Common Base Event format. The Generic Log Adapter simplifies the adoption of the Common Base Event format. The Adapter Configuration Editor and the runtime are components provided by the Generic Log Adapter that will help you create and test transforms quickly. StatCon See Statistical Console. Statistical Console The Statistical Console is a tool that allows you to view graphical representations of statistical data models, both real-time and historical, either individually or grouped. Data is gathered into the statistical model using the Data Collection Framework. Statistical Model A statistical model is a tree-structured model format that contains and persists arbitrary statistical data. Within TPTP, statistical data can be a collection of any data pertinent to the specific operation (or operations) taking place in the platform. Data Collection Framework The Data Collection Framework within TPTP assists in the process of gathering and representing all data in the TPTP workbench. It consists of a remote transport mechanism to collect data, data models to persist this data, loaders to store the data in the models and model specific views for data representation. test case A set of manual or automated steps for evaluating the correctness or performance of a SUT. test suite A collection test cases of a specific type, for example Manual test or JUnit test. Test suites also contain the behaviour or execution sequence of the test cases. location The local or remote target host for the test execution where the SUT resides. Locations also contain general properties describing the target host, used during test execution. workbench location The target host for the workbench based test execution where the SUT resides. Examples of workbench based test types include the JUnit Plug-in test type and the Automated GUI test type. Locations also contain general properties describing the target host and workbench properties describing the target Eclipse instance, used during test execution. artifact Association of test assets, such as test suites and datapools, used during test execution. Test artifacts also contain general properties describing the test assets, used during test execution. deployment Association of deployable artifacts and locations used during test execution. During test execution, artifacts in the deployment are deployed to the local or remote target host identified in the paired location. datapool Collection of variable data used by test cases during test execution. Datapools consist of equivalence classes (tables) containing variables (named and typed columns) and records (rows). Data from datapool variables are used to replace hard-coded input and expected output data in test cases, thus "data-drive" the test. Equivalence classes are usually used to group input data that generate an equivalent pass or fail result. Manual Test A type of test suite for manual testing of a SUT by a human tester. Each test case contains textual steps for manual testing of a SUT. JUnit Test A type of test suite for automated testing of a Java application by a JUnit test class. Each test case is a method in the generated JUnit test class containing user-implemented code for automated testing of a Java application. JUnit test suites can be created by the API Recorder. JUnit Plug-in Test A type of test suite for automated testing of an Eclipse application by a JUnit test class. Each test case is a method in the generated JUnit test class containing user-implemented code for automated testing of an Eclipse application. When executed, JUnit Plug-in tests are run within the context of a newly launched Eclipse Workbench. URL Test A type of test suite for automated testing of a Web application by a JUnit test class. Each test case is a method in the generated JUnit test class containing a HTTP request for automated testing of a Web application. URL test suites can be generated by the URL Test generator. Automated GUI Test A type of test suite for automated GUI testing of an Eclipse application. Each test case contains a macro and optional verification points for automated GUI testing of an Eclipse applications. Automated GUI test suites are generated by using the recording feature in the AGR. HTTP Recorder Proxy-based recorder for capturing HTTP requests and responses from user interaction with a Web application using an Internet browser. Recordings are automatically converted into URL test suites by the URL Test generator for automated testing of a Web application. recorder control Control for starting and stopping a HTTP Recording and observing the status of the active recorder. URL Test generator Generates URL Tests from HTTP recordings after the recording completes. Automated GUI Recorder A testing tool used for regression testing of Eclipse applications. The AGR allows a user to record and playback interactions with the GUI as well as write verification hooks to verify the state of the UI at test time. API Recorder Recorder for capturing API invocations of a Java application based on user-defined filters (package/class/method/signature). Recordings may be converted into JUnit test suites for automated testing of a Java application. System Under Test The software application or system tested by one or more test cases in a test suite. Automatable Services Framework An extensible framework for exposing TPTP functionality to consumers outside of the Eclipse workbench. Examples of available services include execution of tests, interrogation of results and publication of reports. Consumers may invoke ASF services from the commandline, from ant scripts or from Java applications. ASF See Automatable Services Framework. SUT See System Under Test. AGR See Automated GUI Recorder. test log An .execution file generated during a test execution to record test execution results that documents the execution of a test with time stamps and other information, including data regarding deployment, location, individual and overall test verdicts, and test execution event history. The Test Log Viewer is used to view and navigate a test log. execution result See test log. execution history See test log.