TPTP affiliations and status
| key: |
|
done |
|
in progress |
|
todo |
TPTP Platform:
User Interface
User interfaces are provided to manage and access resources used by the Test and Performance Top Level Project. The interfaces also provide the basic user metaphors desired for interacting with remote systems and the resources involved in order to have consistent end user experiences. A basic navigator and many extension points are provided as well as user preferences and facilities to preserve session user state. Along with the basic navigation and extension points, several controls, viewers and editors are also provided in order to give access to all the resources and make common behavior easier.
The User Interface subsystem has the following components:
| Name: |
Status: |
Description: |
| Log View: |
|
A list and property viewer for Common Base Events. |
| Probe Editor: |
|
An Editor of the detailed description of a probe content as well as it’s intended insertion point |
| Sequence Diagrams: |
|
A read only UML 2 sequence diagram that can be bound to any appropriate data source, such as call graphs or machine interactions. |
| Charting Service: |
|
A service that when fed the proper data can be used to render in SWT or SVG standard business graphs for purposes such as reporting test histories or CPU utilization over time. |
| Trace and Profiling perspective: |
|
A single perspective and navigator where trace and monitoring data are shown in the context they were collected in. |
Data Collection and Agents:
An infrastructure is provided to collect data for the various models. This includes the XML fragment specifications that need to be created as well as the model loaders that will load those fragments into the specific model. Where meaningful, service function is provided to assist in creating the instances of these fragments. For example, a correlation service is provided to assist in creating data that can be correlated across machine boundaries. A set of classes to create Common Base Event instances is also provided.
The data collection and agents are made up of the following components:
| Name: |
Status: |
Description: |
| Framework: |
|
The basic control flow infrastructure complete with interfaces for the management of an agent an the data it collects. This includes a large set of predefined XML fragment based events that can be sent and will be loaded into the model as appropriate. |
| JVMPI: |
|
A JVMPI agent used for profiling a JVM as well as sharing class load events for BCI engines. |
| JVMTI: |
|
The Java1.5 replacement for JVMPI. Implementation is TBD. |
| Logging: |
|
A default logging agent for this framework as well as an implementation of a Common Base Event. |
Execution Environment:
A method for controlling an execution environment for a system under test is often needed. From the basics of attaching, starting, and stopping a remote process as well as providing a predefined link to the communication layer is provided in this subsystem of the platform.
A generic runtime that can be driven by a process description is also provided. The initial intent is to use this environment as a generic test behavior implementation that can be used to drive any public interface, especially a web service binding.
The execution environment has the following components:
| Name: |
Status: |
Description: |
| Correlation Engine: |
|
An extension point implementation that associates Common Base Events based on various data value oriented algorithms such as URI and timestamps. |
| Probekit and Byte Code Insertion: |
|
The technology to instrument a class with byte code based on a specification created using the Probekit editor |
| Common Base Event and Logging: |
|
A set of logging interface implementations to match JSR 47, Apache Commons etc. that also suppor the use of common base events, as well as base Eclipse workbench logging. |
| Framework: |
|
A set of APIs and interfaces used to control a separate application. Particularly test execution and monitored applications. |
| Choreography Engine: |
|
A dynamically scriptable engine used to run tests without the requirement of generated code. BPEL is used to define the behavioural flow across the various test services. |
Testing Tools
User Interface:
| Name: |
Status: |
Description: |
| Common Editors: |
|
Editors for test descriptions, behaviour, deployment, and histories are provided over the test model. |
| Data Pool Editor: |
|
An extendable editor for test data pools and support for import of volume data. |
URL Test: |
|
An editor for url targeted testing. |
| Code Coverage: |
|
Method level coverage extensions to the table views. |
| Manual Test client: |
|
A RCP based application that runs remotely to step a user through and record the results of a manual test case. |
| Reporting: |
|
Extension points and usage of SVG and text based execution history reports. |
| Test perspective: |
|
A perspective for creating and managing test artifacts, including histories |
| Automated GUI recorder: |
|
A GUI recorder for Eclipse IDE to automate regression functional testing |
Data Collection and Agents:
The data collection and agents are made up of the following components:
| Name: |
Status: |
Description: |
| Component Test Agent: |
|
An event framework and instance to collect execution results from JUnit and other component based test environments |
| URL request recorder: |
|
A proxy based recorder to intercept and capture url request which can be converted into url test cases. |
Execution Environment:
The execution environment has the following components:
| Name: |
Status: |
Description: |
| Execution Harness: |
|
Common execution environment for test execution |
| Common Runner: |
|
API for all test execution environments to implement |
| Manual Runner: |
|
A runner to drive and control the manual test client |
| JUnit Runner: |
|
A runner to drive and control the JUnit test environment |
| URL Test Runner: |
|
A runner to drive and control the URL test environment |
| Automated GUI runner: |
|
A runner used to playback recorded GUI actions in Eclipse IDE |
Tracing & Profiling
User Interface:
| Name: |
Status: |
Description: |
| Sequence Diagrams: |
|
The common Sequence Diagram is exploited here to show object/class/thread/process/machine interactions over time |
| Statistical and Performance Viewers: |
|
Interactive line charts to show data trends over time, and tabular views to present statistical information about application behavior |
Execution Environment:
The execution environment has the following components:
| Name: |
Status: |
Description: |
| Probe Instances: |
|
Instances of probes and runtimes to support them are provided to do distributed trace. |
Monitoring Tools
User Interface:
| Name: |
Status: |
Description: |
| Generic Log Adapter Configuration editor: |
|
Editor to create, modify, and test Generic Log Adapter configuration files for parsing log files |
| Symptom Catalog Editor: |
|
Editor to create and modify symptom catalogs, sometimes referred to as symptom databases. |
| Log Reports: |
|
Contributions to the Report Wizard in the Log View for generating Eclipse Business Intelligence Reporting Tool (BIRT) reports. |
| Statistical Agent Control View: |
|
View used to select the data to be collected by a statistical agent and displayed in the Statistical views. |
| Managed Agent Explorer: |
|
View used to display, monitor, and edit the properties of a managed resource and invoke operations on a managed resource. Currently support is provided for JMX instrumented java applications. Support for managing resources via Web Services Distributed Management (WSDM) is available as a technology preview. |
| WSDM Tooling: |
|
Note: As of TPTP 4.4, this tooling has moved to the Eclipse COSMOS project. |
Editors and other tooling for generating Web Services Distributed Management (WSDM) manageability endpoints which can be managed with Managed Agent Explorer. This tooling is available as a technology preview.
Data Collection and Agents:
The data collection and agents are made up of the following components:
| Name: |
Status: |
Description: |
| Generic Log Adapter configurations: |
|
Multiple regular expression and static parser configurations for various log formats, that extend the Generic Log Adapter execution environment. |
| Statistical Agents: |
|
TPTP provides statistical agents to monitor and collect Windows and Linux system "perfmon" data, JBoss and JOnAS Application Server JMX data, Apache HTTP server-status data, and MySQL database table and variable data. |
| Monitoring Instrumentation: |
|
Tooling to instrument Java applications for managability using JMX and for logging using Common Base Event. It instruments applications so they can be monitored. This tooling is available as a technology preview. |
Execution Environment:
The execution environment has the following components:
| Name: |
Status: |
Description: |
| Generic Log Adapter: |
|
A runtime that provides support for async log parsing and formatting for redistribution. |