The Eclipse Test and Performance Tools Platform (TPTP) Project addresses the entire test and performance life cycle, from early testing to production application monitoring, including test editing and execution, monitoring, tracing and profiling, and log analysis capabilities. The platform supports a broad spectrum of computing systems including embedded, stand-alone, enterprise, and high-performance and will continue to expand support to encompass the widest possible range of systems.

TPTP version 4.1 has significant new function that makes spanning the test and performance life cycle even easier. Browse the quick tour viewlets of TPTP version 4.1 to learn how you can benefit. The viewlets demonstrate how you could hone a J2EE application.

For your convenience, you can download the sample code used by the viewlets.

1. Profiling a WTP web application using the TPTP profiling tool
   WTP users can use context sensitive pop-up actions and a pre-configured shortcut to profile an application using the TPTP profiling tools.
   
   
2. Creating manual tests for the project
   Create tests for the J2EE project that a human tester will perform.
   
   
3. Creating URL tests for the project
   Automate performance testing of HTTP applications with URL tests.
   
   
4. Profiling the project
   Pinpoint performance and memory problems in the web site.
   
   
5. Analyzing logs and trace
   Combine logs from different sources into a single unit for analysis. Collect detailed runtime information about the program's objects.
   
   
6. Monitoring the project
   Monitor metrics such as the processor time.
   
   
7. Creating BIRT reports based on profiling information
   Use the BIRT report designer to produce custom reports based on profiling information.
   
   
8. New to TPTP 4.1.0.1: Generate BIRT reports based on test execution history, trace and Common Base Event logging models
   TPTP reports organizes information in charts and tables to help users find trends and analyze data.
   

1. Save time and increase stability by automating tests and running tests more often
2. Save aggravation by finding problems in your application faster and with less difficulty
3. Find performance bottlenecks and other metrics easily