1 <contexts> 2 <context id="components" title="Components View"> 3 <description>This view shows the performance results in a hierarchical tree: 4 Component 5 + Scenario 6 + Test machine 7 + Build 8 + Performance numbers 9 10 Typically, the Eclipse builder runs performance tests for each component after the build is made on several performance test machines. Each component defines one or several specific performance test suites made of several test (aka scenario). Several performance numbers (e.g. Elapsed Process Time and CPU Time) are stored for each scenario and all build results are available in the performance results database. 11 12 This structure is roughly the same than the one used to generate performance results, hence make it easy to match the numbers in the corresponding page HTML page.</description> 13 </context> 14 <context id="builds" title="Builds view"> 15 <description>This view shows the list of all the builds contained in the connected database or in the local data files if no database is connected. 16 17 Different fonts are used to display build names depending on the level of knowledge about the corresponding build: 18 - gray+italic: connected to a database but no available local data 19 - gray: connected to a database and local data do not contain any information for this build 20 - black: local data contain information about this build</description> 21 </context> 22 <context id="results" title="Component Results view"> 23 <description>This view show for each of the performance machine the entire results since the beginning. 24 25 Each tab of this view represent a performance machine (also named config). 26 The name of the machine is the name of the tab. The results are displayed in 27 a table where each column represents a scenario and each line a build. 28 The lines are ordered in descending order (from the most recent to the oldest build).</description> 29 </context> 30 </contexts> 31
