Test & Performance Tools Platform (TPTP) Project Plan Summary the open community driving the eclipse platform

Executive Summary of Current Plan

Last revised 06/16/2008 11:35 PM Pacific Time. ( marks interesting changes since the June, 2009)

The Eclipse TPTP Project is currently working on these releases as follows:

Release*	Target Release Date	Description
TPTP 4.6.1	25-Sept-09	TPTP 4.6.1 service release based on Eclipse 3.5 SR1. This release contains defects applied to the TPTP 4.6.1 and not available in TPTP 4.6.0.
TPTP 4.5.2.1	March 2009 to 2010	TPTP 4.5.2.1 limited patch stream based on Eclipse 3.4.2. This limited patch stream consist of multiple milestones. It is only for very selected patches on top of TPTP 4.5.2. All fixes delivered to TPTP v4.5.2.1 are also in the currently active TPTP development stream (e.g. TPTP v4.6).

* Follow links above for access to the respective release plan summaries

The latest supported TPTP releases are as follows:

Release*	Release Date	Description
TPTP 4.6	24-Jun-09	TPTP 4.6 release based on Eclipse 3.5 This release is part of the Eclipse Galileo release. It contains defects applied to the TPTP 4.6 and not available in TPTP 4.5.2.
TPTP 4.5.2	25-Feb-09	TPTP 4.5.2 service release based on Eclipse 3.4 SR2. This release contains defects applied to the TPTP 4.5.2 and not available in TPTP 4.5.1.
TPTP 4.5.1	24-Sept-08	TPTP 4.5.1 service release based on Eclipse 3.4 SR1. This release contains defects applied to the TPTP 4.5.1 and not available in TPTP 4.5.0.
TPTP 4.5	25-June-08	Feature release based on the Eclipse Platform 3.4 release Release part of the Ganymede train.
TPTP_4.4.1	25-February-08	TPTP 4.4.1 fixpack based on Eclipse 3.3.2. This release contains defects applied to the TPTP 4.4.0 Europa maintenance release and not available in TPTP 4.4.0.3.
TPTP_4.4.0.3	28-September-07	TPTP 4.4.0.3 fixpack based on Eclipse 3.3.1.1. This release contains defects applied to the TPTP 4.4.0 Europa maintenance release and not available in TPTP 4.4.0.2.
TPTP_4.4.0	29-June-07	Feature release based on the Eclipse Platform 3.3 release Targeted for new TPTP adopters and legacy adopters who require additional TPTP features/fixes and are ready to move to the Eclipse Platform 3.3 release.
TPTP_4.3.1	19-February-07	TPTP 4.3.1 fixpack based on Eclipse 3.2.1. This release contains defects applied to the TPTP 4.2.2 Callisto maintenance release and not available in TPTP 4.3.
TPTP_4.2.2	09-February-07	Callisto meintenance release The release focus has been Vista tolerance and serious bugs and performance defects found too late to be fixed during the TPTP 4.2.1 release cycle.
TPTP 4.3	04-December-06	Feature release based on the Eclipse Platform 3.2.1 release Targeted for new TPTP adopters and legacy adopters who require additional TPTP features/fixes and are ready to move to the Eclipse Platform 3.2.1 release.
TPTP 4.2.1	29-September-06	Maintenance release based on the Eclipse Platform 3.2.1 release Targeted for new TPTP adopters and legacy adopters who require additional TPTP features/fixes and are ready to move to the Eclipse Platform 3.2.1 release.
TPTP 4.2	30-June-06	Feature release based on the Eclipse Platform 3.2 release Targeted for new TPTP adopters and legacy adopters who require additional TPTP features/fixes and are ready to move to the Eclipse Platform 3.2 release.
TPTP 4.1.0.1	2-February-06	Maintenance release based on the Eclipse Platform 3.1.2 release Targeted for new TPTP adopters and legacy adopters who require additional TPTP features/fixes and are ready to move to the Eclipse Platform 3.1.2 release.
TPTP 4.0.1.2	23-February-06	Maintenance release based on the Eclipse Platform 3.1.2 release Targeted for new TPTP adopters and legacy adopters who require additional TPTP features/fixes and are ready to move to the Eclipse Platform 3.1.2 release.
TPTP 3.3.0.2	2-February-06	Maintenance release based on the Eclipse Platform 3.0.2 release Targeted for legacy adopters of TPTP who require additional TPTP features/fixes, but are not able to move to the Eclipse Platform 3.1 release in this timeframe.

* Follow links above for respective downloads

Our general release philosophy is to release TPTP coincident with Eclipse Platform releases and provide more frequent interim releases as applicable.  This generally translates to an annual major release in June, a minor release around November/December, and maintenance releases as needed. 

Forward Looking Statement

The TPTP PMC adopted and specialized the following Eclipse Themes and Priorities which represent the key focus areas for TPTP enhancements in releases for the year ahead:

· Scaling Up - TPTP will work to enhance the support of large data volumes and processing rates in areas such as data collection, user interface and in the persistence of trace, log and statistical models and execution histories.

· Enterprise Ready - Hooks will be provided within the TPTP infrastructure to link testing tools to requirements tracking tools and defect tracking tools, thus embedding them effectively in enterprise development cycles. Changes to the data collection layers will increase interoperability with enterprise security infrastructure. In addition, there will be progressive adoption of the TPTP tools and infrastructure as a test platform for the project itself, which is in turn likely to drive refinements into the tools. An increased focus on whole-project integration testing will ensure effective interoperability amongst all TPTP components and the rest of the Eclipse environment.

· Design for Extensibility: Be a Better Platform - There will be a wide range of activities within TPTP to externalize APIs and define extension points, making the infrastructure more flexible, and more generic in application. A good example of this is integration of TPTP with WTP and BIRT for web application testing, profiling and generation of customized reports of results.

· Embedded Development - TPTP target execution environment and remote data collection framework provide capabilities that are adapted for high-end embedded systems. TPTP will seek contributions to add support for embedded systems. We are promoting use of TPTP native logging capabilities on a number of embedded target systems.

· Rich Client Platform - TPTP will use RCP for building manual test client and other GUI-based clients in target environments.

· Simple to Use - The existing TPTP tools were conceived as samples, rather than as exemplary. They are deficient in many areas of usability and in some cases lacking in function. The plan is that within the domains which they target they will provide a high-quality user experience out of the box. We will focus on ease of use through enhanced user documentation, tutorials, white papers, demonstrations, and a wide range of enhancements to the user interface to streamline basic processes and clarify concepts and terminology. We are focused on improving as much as possible in Release 4.2, and expect need for continuing this focus beyond 4.2.

· Enable Consistent Multi-language Support - In TPTP a significant effort will be applied in extending coverage of the trace models to represent C/C++ programs and to handle protocol activity (specifically HTTP) consistently with program activity. There will also be C/C++ APIs provided to the data collection and control layers.

· Appealing to the Broader Community - A range of initiatives will be taken to broaden the community of potential and actual users of TPTP. Technically this will include additional integration of open source test tool technologies based on JUnit, and the various hooks to JUnit in the JDT, more data collection agents – particularly focusing on open source technologies, and additional operating system and hardware platforms from which data can be collected. There will be additional marketing and an extensive outreach program to the Eclipse community for additional contribution and adoption.

We are tracking and supporting the following standards and projects:

· We support the OMG UML2 Test Profile and have implemented an early draft of the model. We are assessing the need to change our test model in a future release. Additionally, our members have participated in the definition of the OMG effort to define this model.

· We provide an implementation of Common Base Event which is currently a proposed standard submission to Oasis known as WEF. Once approved we will implement the changes needed to comply with the specification. We also provide an adaptor for JSR47 and for the Eclipse Platform so that applications and Eclipse tools can become producers of this logging format and leverage our analysis tooling.

· We have provided a JVMTI (JSR 163) based data collector to replace our current JVMPI agent. This will improve the install experience as well as improve our coexistence with other infrastructure tooling.

· We are actively working with the Eclipse Platform team support to add support for logical resources and record based resources in order to provide more enterprise and scalable team solutions. This is in line with JSR 147 (logical and record resources) and JSR 170 (logical resources).

· We are also driving extension of our testing and execution frameworks based on other de facto based standards that derive from JUnit, such as HTTPUnit and Abbot.

Release Roadmap Summary

The following illustration summarizes TPTP recent releases and roadmap (TPTP Approved/Pending status refers to TPTP PMC and Planning Group approval status):

For more information, visit the Eclipse Test and Performance Tools Platform (TPTP) Project website.