From Fedora Project Wiki

(Update heap dump test case)
mNo edit summary
 
(One intermediate revision by the same user not shown)
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
# Start another java application, like jedit or Freemeind
|actions=
|actions=
# Select the Java application that you started in the tree on the left
# Select the Java application that you started in the tree on the left and  switch to the "Heap Analyzer" tab
# Switch to the "Heap Analyzer" tab
# Right click anywhere on the graph
# Right click anywhere on the graph and select "Heap Dump"
# Select "Heap Dump"
# In a little while you should see a symbol like "V" on the chart
# In a little while you should see a symbol like "V" on the chart. Double-click on it
# Double click on the "V" symbol
# Switch to the "Object Browser" tab
# Try typing a class name (like "java.util.Map") in the search field in the "Object Browser" tab.
# Try typing a class name (like "java.util.Map") in the search field
[[File:ThermostatSwingHeapDump.png]]
|results=
|results=
# Once you select "Heap Dump", you should see a "v"-like symbol
# 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
# 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
# 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.
# Searching for a class name should display all instances of the class in the Object browser and any referrers and references the instance holds
# No exceptions or error messages should be printed anywhere
# No exceptions or error messages should be printed anywhere
}}
}}

Latest revision as of 00:28, 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 or Freemeind

How to test

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

ThermostatSwingHeapDump.png

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 and any referrers and references the instance holds
  5. No exceptions or error messages should be printed anywhere