From Fedora Project Wiki

(Created page with "{{QA/Test_Case |description=This test case tests whether the heap dump functionality in the Thermostat swing client works correctly. |setup= # Boot into the machine/VM you wis...")
 
(Update heap dump test case)
Line 6: Line 6:
# Start the thermostat storage and agent: {{command|thermostat service &}}
# Start the thermostat storage and agent: {{command|thermostat service &}}
# Start the thermostat Swing client: {{command|thermostat gui}}
# Start the thermostat Swing client: {{command|thermostat gui}}
# Start another java application, like jedit of Freemeind
|actions=
|actions=
# TODO
# Select the Java application that you started in the tree on the left
# Switch to the "Heap Analyzer" tab
# Right click anywhere on the graph and select "Heap Dump"
# In a little while you should see a symbol like "V" on the chart
# Double click on the "V" symbol
# Try typing a class name (like "java.util.Map") in the search field in the "Object Browser" tab.
|results=
|results=
# TODO
# Once you select "Heap Dump", you should see a "v"-like symbol
# Selecting heap dump should cause the heap of the target application to be displayed
# You should be able to switch between the "Histogram" and "Object Browser" tab
# Searching for a class name should display all instances of the class in the Object browser.
# No exceptions or error messages should be printed anywhere
}}
}}

Revision as of 00:14, 23 May 2013

Description

This test case tests whether the heap dump functionality in the Thermostat swing client works correctly.

Setup

  1. Boot into the machine/VM you wish to test.
  2. If thermostat is not installed yet, install thermostat.
  3. Start the thermostat storage and agent: thermostat service &
  4. Start the thermostat Swing client: thermostat gui
  5. Start another java application, like jedit of Freemeind

How to test

  1. Select the Java application that you started in the tree on the left
  2. Switch to the "Heap Analyzer" tab
  3. Right click anywhere on the graph and select "Heap Dump"
  4. In a little while you should see a symbol like "V" on the chart
  5. Double click on the "V" symbol
  6. Try typing a class name (like "java.util.Map") in the search field in the "Object Browser" tab.

Expected Results

  1. Once you select "Heap Dump", you should see a "v"-like symbol
  2. Selecting heap dump should cause the heap of the target application to be displayed
  3. You should be able to switch between the "Histogram" and "Object Browser" tab
  4. Searching for a class name should display all instances of the class in the Object browser.
  5. No exceptions or error messages should be printed anywhere