Debug/Test Script

Java 6.0 Features

• All Instances
  • should not be available when not debugging with 1.6 VM
  • Variables view popup
  • Java Outline view popup (type and constructors only)
  • Java editor popup (type name or constructor name selected)
  • change number of instances to show on Heap walking preference page
• All References
  • should not be available when not debugging with 1.6 VM
  • Variables view popup
  • in-line as variable in the variables view (change in view preferences and preference page)
  • change number of references to show on Heap walking preference page
• Force Early Return
  • should not be available when not debugging with 1.6 VM
  • works as an evaluation (from display and details pane)
  • Run menu and key binding
  • Java editor context menu

Evaluations

• Java 5.0 features
  • Generic types
  • enhanced for loop syntax
  • varargs
  • autoboxing
  • enumerations
• From various contexts
  • Java Compilation Unit editor
  • Java Classfile editor
  • Display View
  • Details area
  • Snippet editor
  • in class files without attached source
  • for arrays as the receiving 'this' context
• Inspect vs. Display
  • note that in the Display view and Snippet editor, "Display" prints the result in-line
  • everywhere else, popups are used to display/inspect the result
• General
  • switch statements should be supported in evaluations
  • use key bindings and context menus
  • use code assist (key binding and context menu)
  • persisting the result - i.e. move the result to the Display view or Expressions view
  • in a clean workspace, popups should size reasonable on the first use, after which the popup sizes are persisted and reused

Context Launching

• Resource properties page
  • available on launchable resources
  • only show listing of launch configurations that apply to selected resource
  • create/delete/edit configuration
  • changes to configurations are cancelable
• Launching
  • launch button(s) tooltip(s) should track selection changes (update as selections change) non-launchable resource should prompt to run the parent (if set to do so, toggle pref on Launching preference page)
  • Running and debugging applications has been simplified to run or debug the selected file or active editor. Use the "Run/Debug > Launching > Launch the selected resource or active editor" preference to enable this behavior. When the selected resource (or active editor) is not executable, you can opt to launch the associated project by selecting "Always launch project if selected resource cannot be launched".
    
    Pressing the Run or Debug toolbar button will launch the selected resource (as will the Run or Debug action in the top level Run menu). When no launch configuration exists for the selected resource, you will be prompted to select how to run or debug an application if there is more than one way to launch the selection. For example, when running a JUnit test you can launch it as a Java application or JUnit test. This will create a launch configuration and entry in the launch history for the application.
    
    When the same resource is launched again, the most recent configuration in the launch history associated with that resource is re-launched.

Launch Options

• Build before launch
  • build is scoped to relevant projects
  • standard job progress dialog is displayed for the following cases. The "Run in Background" button is never present
  • launching in foreground (un-check "Launch in background" option on common tab)
  • waiting for ongoing build to complete before launching
  • building before launching
  • the progress dialog never appears when launching in the background
  • when waiting for an ongoing build to complete before launching a node appears in the debug view in italics showing "waiting for build"
• Prompt to launch in face of compilation errors
  • always/prompt
  • prompt should tell you which project(s) contain errors
  • irrelevant errors should not cause prompt (i.e. Ant errors should not prevent Java launch)
• Prompt to launch in debug mode when breakpoints present
  • always/never/prompt
• General
  • save dirty editors
  • launch in foreground/background (controlled via common tab on launch config)