- 1 Bugzilla Housecleaning Processes
- 2 4.5 Component Reorganization
- 3 Test Tools Project Code Snippets
- 4 See the Wiki_tips Page for Tips on using the Wiki
- 5 How to test TPTP with line level code coverage enabled
- 6 How to "Smoke Test" the new technology agent controller
- 7 4.5 Test Automation Initiative
- 8 Updating the TPTP Project Matrix
- 9 TPTP Build Tools
- 10 TPTP Build
- 11 Different versions of TPTP from a build perspective
- 12 Performance comparisons of the 4.3 "new tech AC" vs. "the RAC" vs. "the IAC"
- 13 Build to Manage
- 14 Profiling problems in 4.4
- 15 TPTP Model
- 16 TPTP Model Scalability
- 17 Eclipse DemoCamp TPTP Presentation
- 18 TPTP Installation with p2 Equinox
- 19 Notes on Building AC on Mac OS X
- 20 4.7 Component Reorganization
- 21 TPTP ramp down policy on Helios
- 22 TPTP retention policy
- 23 TPTP project metrix
See the Wiki_tips Page for Tips on using the Wiki
Here is some information about Build to Manage
Here is little problematic trip down profiling laneProfiling Problems in 4.4
TPTP Model is covered in this page TPTPModel.
TPTP Model Scalability
In TPTP 4.4 there are two effort underway to improve the scalability of the persistence framework. The first is a longer term effort being done jointly with the COSMOS project to define a common set of data services for the kinds of data both projects deal with. This includes log, statistical and trace data as well as network topologies among other things. TPTP collects and provides access to this type of data in support of problem determination tasks done in a development an test environment. This is primarily done through an Eclipse based user interaction. COSMOS target larger scale execution environments than development and unit test, and also provides the prime user experience via a browser. For more information on the TPTP aspects of this effort follow this link. To read about COSMOS follow this link.
The original TPTP DMS page can be found here TPTP data persistence layer, which also contains information about the infrastracture used in the COSMOS EclipseCon 2007 demo.
The second effort is more near term focused but has similar scalability objectives. Basically by using the concepts implemented in the Log Analyzer "large log" support, we will provide an optional RDB storage system for test execution logs. This will optionally load all the data directly into a relational database, and the UI will only query out the needed information. The intent is to remove the current limitation of the Test perspective which holds all data in memory and thus limits the amount of information that can be processed. For more information follow this link.
Eclipse DemoCamp TPTP Presentation